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

Autoscaling policy engine shuffles replicas needlessly and can also suggest nonexistent replicas to be moved

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.6, 8.0
    • Component/s: AutoScaling, SolrCloud
    • Labels:
      None

      Description

      A test that I wrote in SOLR-11066 found the following problem:

      Cluster: 2 nodes
      Collection: 1 shard, 3 replicas, maxShardsPerNode=5
      No autoscaling policy or preference applied

      When the trigger runs, the computed plan needlessly shuffles all three replicas and then proceeds to return suggestions with only numbers as core names. These cores do not exist. I found that these numbers are generated internally by the framework as placeholders for moved cores for further calculations. They should never ever be suggested to the users.

        Attachments

        1. SOLR-11066-failing.patch
          30 kB
          Shalin Shekhar Mangar
        2. SOLR-12023.patch
          5 kB
          Noble Paul

          Issue Links

            Activity

              People

              • Assignee:
                noble.paul Noble Paul
                Reporter:
                shalin Shalin Shekhar Mangar
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: