[
https://issues.apache.org/jira/browse/SOLR-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348043#comment-17348043
]
Noble Paul commented on SOLR-15412:
-----------------------------------
There are 2 possible scenarios
# You update your node to newer node and it refuses to start. Most people have
no clue and the only option is to abandon the upgrade and go back to old Solr
version
# Or if bad data gets into a running cluster , all the nodes and clients go
down immediately and nothing can be restarted without cleaning up the data.
There is also a risk of creating a bad state.json
My suggestion is, all the validations must be added to the "write" code and
just log errors on the "read side". "read side code" should never throw
Exceptions, especially unchecked exceptions. This is the best practice
> Strict validation on Replica metadata can cause complete outage
> ---------------------------------------------------------------
>
> Key: SOLR-15412
> URL: https://issues.apache.org/jira/browse/SOLR-15412
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.5
> Reporter: Ishan Chattopadhyaya
> Priority: Blocker
> Fix For: 8.9
>
>
> More details in SOLR-14245. Intention of this issue is to reduce the impact
> of the changes in SOLR-14245 and immediately issue a breakfix release for the
> users who want to upgrade to 8.5+.
--
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
