lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-9251) Allow a tag role:!overseer in replica placement rules
Date Tue, 06 Dec 2016 04:09:58 GMT

    [ https://issues.apache.org/jira/browse/SOLR-9251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15724268#comment-15724268
] 

Noble Paul commented on SOLR-9251:
----------------------------------

the rule {{rule=shard:RT,role:overseer}}  just does not look right. It means all replicas
 of shard {{RT}} must live in the node which is designated as overseer. why would you want
all replicas of a given shard live in one node? it must be conflicting with {{maxShardsperNode}}
?

Anyway, share your full create command

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message