[
https://issues.apache.org/jira/browse/SOLR-16571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645081#comment-17645081
]
Noble Paul commented on SOLR-16571:
-----------------------------------
{quote}If we think people aren't likely using this and could simply issue a
RELOAD command (why not); let's deprecate and remove this stuff.{quote}
Config API may not work .
Ideally there should be only one watch per node per configset. If there is one
per core , it should be a bug
> Add Java system property for ZooKeeper config watch
> ---------------------------------------------------
>
> Key: SOLR-16571
> URL: https://issues.apache.org/jira/browse/SOLR-16571
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Nick Ginther
> Assignee: Noble Paul
> Priority: Minor
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Solr creates a ZooKeeper watch per-core. On nodes with a lot of cores, this
> results in a lot of ZK watches, and thus increased resource consumption. ZK
> config watches aren't strictly necessary, so we should be able to disable
> them if we want to. To remedy this, we should add a Java system property to
> disable the ZK config watch per core. The default behavior should still be to
> create a ZK config watch per core.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
