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

Cut over implementation of maxShardsPerNode to a collection policy

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: master (9.0)
    • Component/s: AutoScaling, SolrCloud
    • Labels:
      None

      Description

      We've back and forth over handling maxShardsPerNode with autoscaling policies (see SOLR-11005 for history). Now that we've reimplemented support for creating collections with maxShardsPerNode when autoscaling policy is enabled, we should re-look at how it is implemented.

      I propose that we fold maxShardsPerNode (if specified) to a collection level policy that overrides the corresponding default in cluster policy (see SOLR-12845). We'll need to ensure that if maxShardsPerNode is specified then the user sees neither violations nor corresponding suggestions because of the default cluster policy.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ab Andrzej Bialecki
                Reporter:
                shalin Shalin Shekhar Mangar
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 1h
                  1h