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

Replication can still cause index corruption.

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

Details

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

    Description

      While we have plugged most of these holes, there appears to be another that is fairly rare.

      I've seen it play out a couple ways in tests, but it looks like part of the problem is that even if we decide we need a file and download it, we don't care if we then cannot move it into place if it already exists.

      I'm working with a fix that does two things:

      • Fail a replication attempt if we cannot move a file into place because it already exists.
      • If a replication attempt during recovery fails, on the next attempt force a full replication to a new directory.

      Attachments

        1. SOLR-7134.patch
          27 kB
          Mark Miller
        2. SOLR-7134.patch
          27 kB
          Mark Miller
        3. SOLR-7134.patch
          23 kB
          Mark Miller
        4. SOLR-7134.patch
          22 kB
          Mark Miller
        5. SOLR-7134.patch
          17 kB
          Mark Miller

        Issue Links

        Activity

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

          People

            markrmiller@gmail.com Mark Miller
            markrmiller@gmail.com Mark Miller
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment