[
https://issues.apache.org/jira/browse/SOLR-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18119188#comment-18119188
]
David Smiley commented on SOLR-18131:
-------------------------------------
We do want ZK behind the scenes but it isn't going away. It's the most "load
bearing" thing in SolrCloud. Note that this proposal doesn't increase the ZK
exposure; this proposes a _different_ way to do what we're doing today. And
even though it's technically in the public API; it's an optional header
exchange detail for a client that wishes to use it.
SSE seems great for keeping a browser's webpage up-to-date on a very dynamic
site but I question it's use by CloudSolrClient specifically, which I think is
what your proposal implies. The proposal above is very light-weight by
comparison – no active connection. The client doesn't need to know about all
things in the cluster; it only needs to know about the state pertinent to the
requests it's making (since it's routing them).
> SolrCloud should return HTTP header(s) of certain ZK node versions
> ------------------------------------------------------------------
>
> Key: SOLR-18131
> URL: https://issues.apache.org/jira/browse/SOLR-18131
> Project: Solr
> Issue Type: Sub-task
> Reporter: David Smiley
> Priority: Major
>
> (see parent issue) Solr should return an HTTP header of some ZK Stat version
> numbers of pertinent ZK nodes. Relates to ClusterState tracking. This
> enables a client to invalidate a cache of related information (perhaps
> CloudSolrClient / HttpClusterStateProvider) or similar for custom clients not
> using SolrJ.
> It could be JSON to hold multiple, or we use multiple headers. Need to
> decide on suitable name(s).
> All SolrCloud interaction can use this:
> live_nodes: ZK cversion (initial 'c' is for children)
> Interactions involving one (typical) or more collections can incorporate:
> collectionName: ZK version
> Interactions involving alias resolution can incorporate:
> aliases: ZK version
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
