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

Deprecate maxSHardsPerNode when autoscaling policies are used

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

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 7.0
    • 7.0, 8.0
    • None
    • None

    Description

      We have found out that maxShardPerNode is not compatible with the new auto scaling policies. So we need to deprecate that parameter when the autoscaling policies are used.

      the bin/solr script passes that parameter all the time irrespective of whether the user needs it or not.

      We need to fix it for 7.0 itself

      Attachments

        1. SOLR-11239.patch
          14 kB
          Shalin Shekhar Mangar
        2. SOLR-11239.patch
          16 kB
          Noble Paul

        Issue Links

        relates to

        Bug - A problem which impairs or prevents the functions of the product. SOLR-11807 maxShardsPerNode=-1 needs special handling while restoring collections

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

        Improvement - An improvement or enhancement to an existing feature or task. SOLR-11005 inconsistency when maxShardsPerNode used along with policies

        • Major - Major loss of function.
        • Closed

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

          People

            noble.paul Noble Paul
            noble.paul Noble Paul
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment