[jira] [Commented] (SOLR-5609) Don't let cores create slices/named replicas

["Noble Paul (JIRA)" <ji...@apache.org>]

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

Noble Paul commented on SOLR-5609:
----------------------------------

Takeaway from my discussion with [~markrmiller@gmail.com] .

 If legacyCloud=false , delete the "collection1" or "defaultcol" cores when they send the STATE commands


> Don't let cores create slices/named replicas
> --------------------------------------------
>
>                 Key: SOLR-5609
>                 URL: https://issues.apache.org/jira/browse/SOLR-5609
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Noble Paul
>             Fix For: 5.0, 4.7
>
>
> In SolrCloud, it is possible for a core to come up in any node , and register itself with an arbitrary slice/coreNodeName. This is a legacy requirement and we would like to make it only possible for Overseer to initiate creation of slice/replicas
> We plan to introduce cluster level properties at the top level
> /cluster-props.json
> {code:javascript}
> {
> "noSliceOrReplicaByCores":true"
> }
> {code}
> If this property is set to true, cores won't be able to send STATE commands with unknown slice/coreNodeName . Those commands will fail at Overseer. This is useful for SOLR-5310 / SOLR-5311 where a core/replica is deleted by a command and  it comes up later and tries to create a replica/slice



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org