[
https://issues.apache.org/jira/browse/SOLR-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104562#comment-13104562
]
Yonik Seeley commented on SOLR-2765:
------------------------------------
- we probably want states on a per shard basis (in case we go with
micro-sharding, a node may have multiple shards in different states).
- we might want a state on the node also... a way to mark it as "disabled" in
general (note to rest of cluster - consider the node to be down)
- an active/enabled shard should be preferred as a leader
Perhaps at the same time thing of adding "roles" to nodes. A comma separated
list of values that have some pre-defined values, but that the user may also
choose to define their own values. One example use case would be to have a
bank of indexers for rich text (PDF, Word, etc) that do all the work of text
extraction or other expensive processing and forward the results to the right
leader. This could also be used to remove all search traffic from a node (by
removing the standard "searcher" role) but allow it to stay up-to-date by
remaining in the indexing loop.
> Shard/Node states
> -----------------
>
> Key: SOLR-2765
> URL: https://issues.apache.org/jira/browse/SOLR-2765
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud, update
> Reporter: Yonik Seeley
> Fix For: 4.0
>
>
> Need state for shards that indicate they are recovering, active/enabled, or
> disabled.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
