[
https://issues.apache.org/jira/browse/SOLR-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376118#comment-15376118
]
Hrishikesh Gadre commented on SOLR-9106:
----------------------------------------
We found a scenario where the ZK watch was not fired in a timely fashion
resulting in the unit test failure (SOLR-9242). The changes made to fix that
failure are exactly opposite to the intent of this JIRA (i.e. it brings back
the old behavior).
https://github.com/apache/lucene-solr/commit/eefdc62c997f7936b6db203111d8149dc934b243
I agree with Nobel here. [~romseygeek] is reading cluster properties every-time
a serious performance problem?
CC [~varunthacker]
> 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]
