You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2025/01/08 17:48:00 UTC
[jira] [Commented] (SOLR-17616) CloudSolrClient admin routing should consider node roles and randomization
[ https://issues.apache.org/jira/browse/SOLR-17616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911188#comment-17911188 ]
David Smiley commented on SOLR-17616:
-------------------------------------
If node roles aren't in-use, perhaps admin commands *about* a collection should be handled differently – delivered to a node hosting a replica of that collection.
> CloudSolrClient admin routing should consider node roles and randomization
> --------------------------------------------------------------------------
>
> Key: SOLR-17616
> URL: https://issues.apache.org/jira/browse/SOLR-17616
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud, SolrJ
> Reporter: David Smiley
> Priority: Minor
>
> CloudSolrClient delivers an admin request to the same node given a list of liveNodes (no ordering). If it's a V2 request, it'll be randomly chosen, which is a little better. If the non-Overseer so-called "distributed" cluster processing booleans are set, it's preferable to more thoughtfully distribute this work instead of consistently picking the same node. Node roles are an existing way of designating nodes for certain purposes.
> Instead, CloudSolrClient should pick randomly amongst the OVERSEER node roles, then amongst the COORDINATOR node roles, then amongst remaining.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org