[
https://issues.apache.org/jira/browse/SOLR-14245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346834#comment-17346834
]
Andrzej Bialecki commented on SOLR-14245:
-----------------------------------------
Jira is for tracking technical issues, and not discussing our attitudes,
whether real or implied. "We are callous" is a blank statement to which I don't
subscribe.
This issue is more than a year old - I think that instead of reopening it a
separate Jira should be created to discuss the proper fix. I'm unwilling to
simply revert it because (as I explained above) the purpose of this change is
still valid - it's important to be aware that a piece of a critical Solr state
is corrupted. Let's open a new Jira and discuss the fix.
> 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-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
