[
https://issues.apache.org/jira/browse/SOLR-14219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024249#comment-17024249
]
Andy Webb commented on SOLR-14219:
----------------------------------
We have a (non-production) cluster with three nodes - two are running 8.4.1,
the third has 8.5.0 with {{useUnsafeOverseerResponse=true}}. This simulates the
situation we'd have part-way through a rolling update in production.
If one of the 8.4.1 nodes is the overseer, requesting
{{/solr/admin/collections?action=overseerstatus}} on the other 8.4.1 node is
OK, but on the 8.5.0 node it triggers an {{InvalidClassException}}. If the
8.5.0 node is the overseer, that request to either of the 8.4.1 nodes triggers
the exception.
With the fix in the PR in place to force the new version of
OverseerSolrResponse to have the same serialVersionUID as before, all three
nodes' overseers are compatible.
(NB an 8.4.0 node would not be compatible with earlier or newer versions due to
its SolrResponse having a different UID - that's what led to SOLR-14165.)
> OverseerSolrResponse's serialVersionUID has changed
> ---------------------------------------------------
>
> Key: SOLR-14219
> URL: https://issues.apache.org/jira/browse/SOLR-14219
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Andy Webb
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When the {{useUnsafeOverseerResponse=true}} option introduced in SOLR-14095
> is used, the serialized OverseerSolrResponse has a different serialVersionUID
> to earlier versions, making it backwards-incompatible.
> https://github.com/apache/lucene-solr/pull/1210 forces the serialVersionUID
> to its old value, so old and new nodes become compatible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
