[
https://issues.apache.org/jira/browse/SOLR-9251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15723258#comment-15723258
]
David Smiley commented on SOLR-9251:
------------------------------------
[~noble.paul] does the rule system allow one to have this rule but specify
further that a particular shard may go on this overseer node (or any designated
node for that matter)? I hoped this would work:
{{&rule=shard:RT,role:overseer}}
{{&rule=shard:!RT,role:!overseer}}
This is a collection with the implicit router and thus named shards; one of
them named "RT". When I do this, Solr complains when attempting to create a
replica that it could not identify nodes matching the rules. Note that this
notion isn't specific to the overseer... I have also tried with
{{host:specifcHostName}} and got the same result. I've tried various ways to
try and achieve this but all in vain :-(
(apologies if you'd rather me ask on the user list)
> Allow a tag role:!overseer in replica placement rules
> -----------------------------------------------------
>
> Key: SOLR-9251
> URL: https://issues.apache.org/jira/browse/SOLR-9251
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Assignee: Noble Paul
> Fix For: 6.2
>
> Attachments: SOLR-9251.patch
>
>
> The reason to assign an overseer role to a node is to ensure that the node
> is exclusively used as overseer. replica placement should support tag called
> {{role}}
> So if a collection is created with {{rule=role:!overseer}} no replica should
> be created in nodes designated as overseer
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
