Consider storing resharding validation initial count individually per donor

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The coordinator currently updates the count progress for each donor after it gets the results from all the donors and updates them in one go. If we split the update to the coordinator doc as we get response from each donor, then the coordiantor will be able minimize repeated work after a failover if there's only a single shard that has not returned results for count.

            Assignee:
            Unassigned
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: