[ https://issues.apache.org/jira/browse/SOLR-11654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511776#comment-16511776 ]
Gus Heck commented on SOLR-11654: --------------------------------- New patch with TrackingUpdateProcessorFactory class (for test use only) and unit test utilizing it to test that docs are now routed to the shard leader. Just realized I didn't yet investigate the null for RetryNode... I'll look at that and add another patch if it seems to worry me > TimePartitionedUpdateProcessor.lookupShardLeaderOfCollection should route to > the ideal shard > -------------------------------------------------------------------------------------------- > > Key: SOLR-11654 > URL: https://issues.apache.org/jira/browse/SOLR-11654 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud > Reporter: David Smiley > Assignee: David Smiley > Priority: Major > Attachments: SOLR-11654.patch, SOLR-11654.patch > > > {{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. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org