You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "Houston Putman (Jira)" <ji...@apache.org> on 2025/01/13 21:50:00 UTC

[jira] [Commented] (SOLR-17620) Encode the version of Solr in SolrCloud "liveNode"

    [ https://issues.apache.org/jira/browse/SOLR-17620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912669#comment-17912669 ] 

Houston Putman commented on SOLR-17620:
---------------------------------------

I'm all for this. A json object with (limited) node info would be great.

> Encode the version of Solr in SolrCloud "liveNode"
> --------------------------------------------------
>
>                 Key: SOLR-17620
>                 URL: https://issues.apache.org/jira/browse/SOLR-17620
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: David Smiley
>            Priority: Major
>
> This proposal is for the "live node" (ZkController.createEphemeralLiveNode) stored in ZK to have a JSON payload with the SolrVersion and other interesting metadata like the node roles.  Furthermore, ZkStateReader should read this state and provide a method like getLowestSolrVersion().
> This foundational mechanism allows us to evolve SolrCloud safely using an in-place rolling upgrade strategy.  Features that need to behave differently can consult the lowest SolrVersion to react accordingly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org