Solr
  1. Solr
  2. SOLR-4511

Repeater doesn't return correct index version to slaves

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.1
    • Fix Version/s: 4.2, 6.0
    • Component/s: replication (java)
    • Labels:
      None

      Description

      Related to SOLR-4471. I have a master-repeater-2slaves architecture. The replication between master and repeater is working fine but slaves aren't able to replicate because their master (repeater node) is returning an old index version, but in admin UI the version that repeater have is correct.

      When I do http://localhost:17045/solr/replication?command=indexversion response is: <long name="generation">29037</long> when the version should be 29042

      If I restart the repeater node this URL returns the correct index version, but after a while it fails again.

      1. o8uzad.jpg
        653 kB
        Raúl Grande
      2. SOLR-4511.patch
        13 kB
        Mark Miller

        Issue Links

          Activity

          Hide
          Mark Miller added a comment -

          I don't see a repeater test. I can look at adding one.

          Show
          Mark Miller added a comment - I don't see a repeater test. I can look at adding one.
          Hide
          Mark Miller added a comment -

          It would help if you could track down some reproduction steps. I have a repeater test with a master, repeater, and slave. So far my tests seem fine, so I'm not tickling whatever you are seeing.

          Show
          Mark Miller added a comment - It would help if you could track down some reproduction steps. I have a repeater test with a master, repeater, and slave. So far my tests seem fine, so I'm not tickling whatever you are seeing.
          Hide
          Mark Miller added a comment -

          I added a new repeater test, but it doesn't tickle what you are seeing.

          I did add some checks of the replicatable commit vs the current commit point though, and that caused another test to find an issue. I've fixed that, and I think it was probably causing your issue as well.

          Show
          Mark Miller added a comment - I added a new repeater test, but it doesn't tickle what you are seeing. I did add some checks of the replicatable commit vs the current commit point though, and that caused another test to find an issue. I've fixed that, and I think it was probably causing your issue as well.
          Hide
          Raúl Grande added a comment -

          Thank you, I will try to install the patch asap. If I find any issues I will let you know.

          Show
          Raúl Grande added a comment - Thank you, I will try to install the patch asap. If I find any issues I will let you know.
          Hide
          Mark Miller added a comment -

          Thanks Raul! Look forward to hearing your results.

          Show
          Mark Miller added a comment - Thanks Raul! Look forward to hearing your results.
          Hide
          Mark Miller added a comment -

          I've committed this and merged back to 4X - unfortunetly, I used the wrong commit msg for the 4.X merge back though, so it won't be tagged in JIRA correctly.

          Let me know how it works Raul.

          Show
          Mark Miller added a comment - I've committed this and merged back to 4X - unfortunetly, I used the wrong commit msg for the 4.X merge back though, so it won't be tagged in JIRA correctly. Let me know how it works Raul.
          Hide
          Commit Tag Bot added a comment -

          [trunk commit] Mark Robert Miller
          http://svn.apache.org/viewvc?view=revision&revision=1451659

          SOLR-4511: When a new index is replicated into place, we need to update the most recent replicatable index point without doing a commit. This is important for repeater use cases, as well as when nodes may switch master/slave roles.

          Show
          Commit Tag Bot added a comment - [trunk commit] Mark Robert Miller http://svn.apache.org/viewvc?view=revision&revision=1451659 SOLR-4511 : When a new index is replicated into place, we need to update the most recent replicatable index point without doing a commit. This is important for repeater use cases, as well as when nodes may switch master/slave roles.
          Hide
          Aditya added a comment -

          I had similar issue .. did check with trunk build deployed on my dev environment and its now replicates properly even with the incremental index.

          Show
          Aditya added a comment - I had similar issue .. did check with trunk build deployed on my dev environment and its now replicates properly even with the incremental index.
          Hide
          Mark Miller added a comment -

          Great, thanks for the info.

          Show
          Mark Miller added a comment - Great, thanks for the info.
          Hide
          Steve Rowe added a comment -

          Bulk move 4.4 issues to 4.5 and 5.0

          Show
          Steve Rowe added a comment - Bulk move 4.4 issues to 4.5 and 5.0

            People

            • Assignee:
              Mark Miller
              Reporter:
              Raúl Grande
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development