Make allocateBucket create a new bucketId when there is a bucketId collision in the bucketStateRegistry

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Execution Team 2024-07-08, Execution Team 2024-07-22, Execution Team 2024-08-19, Execution Team 2024-09-16
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, when we try to allocate a new bucket in memory, if we encounter errors when trying to initialize the bucket state, we will throw a Write Conflict Exception here. It does not look like this is currently handled, and if this exception is thrown the write is failed. These errors should be able to be avoided by retrying the insert at a higher level.

              Assignee:
              Damian Wasilewicz
              Reporter:
              Damian Wasilewicz
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: