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

During replication use checksums to verify if files are the same

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

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • None
    • 5.0, 6.0
    • replication (java)
    • None

    Description

      Currently we check if an index file on the master and slave is the same by checking if it's name and file length match.

      With LUCENE-2446 we now have a checksums for each index file in the segment. We should leverage this to verify if two files are the same.

      Places like SnapPuller.isIndexStale and SnapPuller.downloadIndexFiles should check against the checksum also.

      Attachments

        1. SOLR-6920-5x.patch
          18 kB
          Mark Miller
        2. SOLR-6920-5x.patch
          18 kB
          Mark Miller
        3. SOLR-6920-5x.patch
          19 kB
          Mark Miller
        4. SOLR-6920-5x.patch
          19 kB
          Mark Miller
        5. SOLR-6920.patch
          12 kB
          Varun Thacker
        6. SOLR-6920.patch
          11 kB
          Varun Thacker
        7. SOLR-6920.patch
          9 kB
          Varun Thacker
        8. SOLR-6920.patch
          15 kB
          Mark Miller
        9. SOLR-6920.patch
          17 kB
          Mark Miller
        10. SOLR-6920.patch
          16 kB
          Varun Thacker

        Issue Links

        is depended upon by

        Bug - A problem which impairs or prevents the functions of the product. SOLR-6640 Replication can cause index corruption.

        • Blocker - Blocks development and/or testing work, production could not run
        • Closed
        is related to

        Bug - A problem which impairs or prevents the functions of the product. SOLR-7134 Replication can still cause index corruption.

        • Critical - Crashes, loss of data, severe memory leak.
        • Closed
        relates to

        Improvement - An improvement or enhancement to an existing feature or task. SOLR-7093 Cleanup comment and move hardcoded value of file size to replicate to a final

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Open

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            markrmiller@gmail.com Mark Miller
            varun Varun Thacker
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment