You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2014/11/23 16:56:12 UTC

[jira] [Commented] (SOLR-6370) Allow tests to report/fail on many ZK watches being parallelly requested on the same data

    [ https://issues.apache.org/jira/browse/SOLR-6370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222398#comment-14222398 ] 

Mark Miller commented on SOLR-6370:
-----------------------------------

Hey [~thelabdude], have you finished this one? Looks like one commit to trunk, unassigned, and still open?

> 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
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org