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

Replica assignments should try to take the host name into account so all replicas don't end up on the same host

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: SolrCloud
    • Labels:
      None

      Description

      I have 18 SolrCloud nodes distributed across 3 Ec2 instances, so 6 per instance. One of my collections was created with all replicas landing on different SolrCloud nodes on the same instance. Ideally, SolrCloud would be a little smarter and ensure that at least one of the replicas was on one of the other hosts.

      shard4: {
      http://ec2-??-??-??-239.compute-1.amazonaws.com:8988/solr/med_collection_shard4_replica1/ LEADER
      http://ec2-??-??-??-239.compute-1.amazonaws.com:8984/solr/med_collection_shard4_replica3/
      http://ec2-??-??-??-239.compute-1.amazonaws.com:8985/solr/med_collection_shard4_replica2/
      }

      I marked this as minor for now as it could be argued that I shouldn't be running that many Solr nodes per instance, but I'm seeing plenty of installs that are using higher-end instance types / server hardware and then running multiple Solr nodes per host.

        Attachments

        1. SOLR-6027.patch
          4 kB
          Noble Paul

          Issue Links

            Activity

              People

              • Assignee:
                noble.paul Noble Paul
                Reporter:
                thelabdude Timothy Potter
              • Votes:
                2 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated: