[
https://issues.apache.org/jira/browse/SOLR-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381858#comment-15381858
]
Noble Paul commented on SOLR-9106:
----------------------------------
bqThis seems exactly backwards to me? Watches are pretty lightweight. Do you
have some numbers here
The problem with watches is that we really don't know when the changes are
propagated to each node. If we read the data just in time we always get the
latest data. Watching is light weight, I haven't done any benchmarking yet.
> Cache cluster properties in ZkStateReader
> -----------------------------------------
>
> Key: SOLR-9106
> URL: https://issues.apache.org/jira/browse/SOLR-9106
> Project: Solr
> Issue Type: Improvement
> Affects Versions: master (7.0)
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Fix For: 6.1
>
> Attachments: SOLR-9106.patch, SOLR-9106.patch
>
>
> ZkStateReader currently makes calls into ZK every time getClusterProps() is
> called. Instead we should keep the data locally and use a Watcher to update
> it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
