[
https://issues.apache.org/jira/browse/SOLR-6370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227793#comment-14227793
]
ASF subversion and git services commented on SOLR-6370:
-------------------------------------------------------
Commit 1642181 from [~thelabdude] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1642181 ]
SOLR-6370: oops, put wrong jira # in changes.txt
> Allow tests to report/fail on many ZK watches being parallelly requested on
> the same data
> -----------------------------------------------------------------------------------------
>
> Key: SOLR-6370
> URL: https://issues.apache.org/jira/browse/SOLR-6370
> Project: Solr
> Issue Type: Improvement
> Components: Tests
> Reporter: Ramkumar Aiyengar
> Priority: Minor
> Fix For: 5.0
>
>
> Issues like SOLR-6336 uncovered cases where we were using too many ZK
> watches. Watches are costly and we should fix such places but there's no good
> way for tests to find out about them.
> This issue is for a mechanism for tests to report or fail on watches being
> redundantly set on data. This would also allow for specific tests to
> configure if there's a valid case for such a thing happening.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
