[
https://issues.apache.org/jira/browse/SOLR-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048136#comment-16048136
]
Tomás Fernández Löbbe commented on SOLR-10879:
----------------------------------------------
OK, I see that this validation is only done when you delete replicas by count,
not if you delete replicas by name (which is what {{DeleteNodeCmd}} does)
> DELETEREPLICA and DELETENODE commands should prevent data loss when
> replicationFactor==1
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-10879
> URL: https://issues.apache.org/jira/browse/SOLR-10879
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.6, master (7.0), 6.7
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
>
> There should be some level of protection against inadvertent data loss when
> issuing these commands when replicationFactor is 1 - deleting a node or a
> replica in this case will be equivalent to completely deleting some shards.
> This is further complicated by the replica types - there could be still
> remaining replicas after the operation, but if they are all of PULL type then
> none of them will ever become a shard leader.
> We could require that the command should fail in such case unless a boolean
> option "force==true" is specified.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
