Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-11299 Time partitioned collections (umbrella issue)
  3. SOLR-11654

TimePartitionedUpdateProcessor.lookupShardLeaderOfCollection should route to the ideal shard

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.5
    • Component/s: SolrCloud
    • Labels:
      None

      Description

      TimePartitionedUpdateProcessor.lookupShardLeaderOfCollection looks up the Shard/Slice to talk to for the given collection. It currently picks the first active Shard/Slice but it has a TODO to route to the ideal one based on the router configuration of the target collection. There is similar code in CloudSolrClient & DistributedUpdateProcessor that should probably be refactored/standardized so that we don't have to repeat this logic.

        Attachments

        1. SOLR-11654.patch
          22 kB
          Gus Heck
        2. SOLR-11654.patch
          33 kB
          Gus Heck
        3. SOLR-11654.patch
          33 kB
          Gus Heck
        4. SOLR-11654.patch
          30 kB
          David Smiley
        5. SOLR-11654.patch
          30 kB
          Gus Heck

          Activity

            People

            • Assignee:
              dsmiley David Smiley
              Reporter:
              dsmiley David Smiley
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: