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

The autoAddReplica feature can result in SolrCores being assigned new shards.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.6, 7.0
    • Component/s: None
    • Security Level: Public (Default Security Level. Issues are Public)
    • Labels:
      None

      Issue Links

        Activity

        Hide
        markrmiller@gmail.com Mark Miller added a comment -

        There is also a check that breaks this and the feature to have coreNodeName be used for taking over existing registrations. I'll remove it.

        Show
        markrmiller@gmail.com Mark Miller added a comment - There is also a check that breaks this and the feature to have coreNodeName be used for taking over existing registrations. I'll remove it.
        Hide
        jira-bot ASF subversion and git services added a comment -

        Commit bac3424936eacb2381138612ca70276ef5f909d5 in lucene-solr's branch refs/heads/master from markrmiller
        [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=bac3424 ]

        SOLR-10279: The autoAddReplica feature can result in SolrCores being assigned new shards when using legacyCloud=false and will also fail on a state check when taking over a core registration with a new core.

        Show
        jira-bot ASF subversion and git services added a comment - Commit bac3424936eacb2381138612ca70276ef5f909d5 in lucene-solr's branch refs/heads/master from markrmiller [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=bac3424 ] SOLR-10279 : The autoAddReplica feature can result in SolrCores being assigned new shards when using legacyCloud=false and will also fail on a state check when taking over a core registration with a new core.
        Hide
        jira-bot ASF subversion and git services added a comment -

        Commit 5983f9e702a9dbd1ba9c5f383c8cc310d00fde91 in lucene-solr's branch refs/heads/branch_6x from markrmiller
        [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5983f9e ]

        SOLR-10279: The autoAddReplica feature can result in SolrCores being assigned new shards when using legacyCloud=false and will also fail on a state check when taking over a core registration with a new core.

        Show
        jira-bot ASF subversion and git services added a comment - Commit 5983f9e702a9dbd1ba9c5f383c8cc310d00fde91 in lucene-solr's branch refs/heads/branch_6x from markrmiller [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5983f9e ] SOLR-10279 : The autoAddReplica feature can result in SolrCores being assigned new shards when using legacyCloud=false and will also fail on a state check when taking over a core registration with a new core.
        Hide
        markrmiller@gmail.com Mark Miller added a comment -

        Originally this was titled for SOLR-10279 legacyCloud=false, but there appear to be harder to hit in a test but similar issues with lagacyCloud=true.

        Show
        markrmiller@gmail.com Mark Miller added a comment - Originally this was titled for SOLR-10279 legacyCloud=false, but there appear to be harder to hit in a test but similar issues with lagacyCloud=true.

          People

          • Assignee:
            markrmiller@gmail.com Mark Miller
            Reporter:
            markrmiller@gmail.com Mark Miller
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development