You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Noble Paul (Jira)" <ji...@apache.org> on 2021/05/18 02:47:00 UTC
[jira] [Commented] (SOLR-14245) Validate Replica / ReplicaInfo on
creation
[ https://issues.apache.org/jira/browse/SOLR-14245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346547#comment-17346547 ]
Noble Paul commented on SOLR-14245:
-----------------------------------
This has caused a cluster outage in our datacenter
I can't understand what is the point in throwing these errors with no way of handling those errors
Basically , our nodes can't restart if there is a small error in state.json. Previously the cluster used to start but only those replicas were down.
Let's revert this
> Validate Replica / ReplicaInfo on creation
> ------------------------------------------
>
> Key: SOLR-14245
> URL: https://issues.apache.org/jira/browse/SOLR-14245
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Minor
> Fix For: 8.5
>
>
> Replica / ReplicaInfo should be immutable and their fields should be validated on creation.
> Some users reported that very rarely during a failed collection CREATE or DELETE, or when the Overseer task queue becomes corrupted, Solr may write to ZK incomplete replica infos (eg. node_name = null).
> This problem is difficult to reproduce but we should add safeguards anyway to prevent writing such corrupted replica info to ZK.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org