Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-11216

Race condition in peerSync

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 7.4
    • Fix Version/s: 7.5, 8.0
    • Component/s: None
    • Labels:
      None

      Description

      When digging into SOLR-10126. I found a case that can make peerSync fail.

      • leader and replica receive update from 1 to 4
      • replica stop
      • replica miss updates 5, 6
      • replica start recovery
        1. replica buffer updates 7, 8
        2. replica request versions from leader,
        3. in the same time leader receive update 9, so it will return updates from 1 to 9 (for request versions) when replica get recent versions ( so it will be 1,2,3,4,5,6,7,8,9 )
        4. replica do peersync and request updates 5, 6, 9 from leader
        5. replica apply updates 5, 6, 9. Its index does not have update 7, 8 and maxVersionSpecified for fingerprint is 9, therefore compare fingerprint will fail

        Attachments

        1. SOLR-11216.patch
          79 kB
          Cao Manh Dat
        2. SOLR-11216.patch
          78 kB
          Cao Manh Dat
        3. SOLR-11216.patch
          73 kB
          Cao Manh Dat
        4. SOLR-11216.patch
          72 kB
          Cao Manh Dat
        5. SOLR-11216.patch
          45 kB
          Cao Manh Dat
        6. SOLR-11216.patch
          21 kB
          Cao Manh Dat
        7. SOLR-11216.patch
          11 kB
          Cao Manh Dat

        Issue Links

          Activity

            People

            • Assignee:
              caomanhdat Cao Manh Dat
              Reporter:
              caomanhdat Cao Manh Dat

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment