[ https://issues.apache.org/jira/browse/SOLR-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrzej Bialecki resolved SOLR-10879. -------------------------------------- Resolution: Fixed Fix Version/s: master (8.0) 7.0 > 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, 7.0, 6.7 > Reporter: Andrzej Bialecki > Assignee: Andrzej Bialecki > Fix For: 7.0, master (8.0) > > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org