Rename coordinator must treat the primary shard as a participant

XMLWordPrintableJSON

    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The rename coordinator must not make distinctions between the primary shard and any other shard.

      As a precondition for a unique rename recovery procedure, include also the primary shard when sending commands to all participants to manage critical section, range deletions and local rename.

              Assignee:
              Pierlauro Sciarelli
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: