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

Autoscaling based replica placement is broken out of the box

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

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 7.6, 7.7
    • 7.7.1, 8.0, 9.0
    • AutoScaling
    • None

    Description

      SOLR-12739 made autoscaling as the default replica placement strategy. However in the absence of SOLR-12845, replicas can be placed without any regards for maxShardsPerNode causing multiple replicas of the same shard to be placed on the same node together. Also it was reported in SOLR-13247 that createNodeSet is not being respected as well.

      SOLR-13159 was an early signal of the problem but it was not reproducible and there was a DNS problem in the cluster too so the root cause was not clear then.

      I am creating this blocker issue because as it stands today, we cannot guarantee the layout of new collections. At a minimum, we should revert to using the legacy replica assignment policy or add default policies with SOLR-12845 and have createNodeSet work. Related but not mandatory would be to fix SOLR-12847 as well.

      Attachments

        1. SOLR-13248-withDefaultCollectionProp.patch
          7 kB
          Jan Høydahl
        2. SOLR-13248-branch7x-backport.patch
          12 kB
          Ishan Chattopadhyaya
        3. SOLR-13248.patch
          4 kB
          Shalin Shekhar Mangar
        4. SOLR-13248.patch
          10 kB
          Shalin Shekhar Mangar
        5. SOLR-13248.patch
          12 kB
          Shalin Shekhar Mangar

        Issue Links

        Activity

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

          People

            shalin Shalin Shekhar Mangar
            shalin Shalin Shekhar Mangar
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment