curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <>
Subject [jira] [Commented] (CURATOR-21) PathChildrenCache consumes an entire thread all the time no matter what
Date Sun, 05 May 2013 14:10:15 GMT


Jordan Zimmerman commented on CURATOR-21:

I'm now wondering if the collation of operations is no longer correct. In the previous implementation,
pending operations that were exactly the same were coalesced. In this implementation, a refresh
that is to be queued while a refresh is in process gets dropped. I need to think about this
more but I believe it's incorrect.
> PathChildrenCache consumes an entire thread all the time no matter what
> -----------------------------------------------------------------------
>                 Key: CURATOR-21
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.0.0
>            Reporter: Eric Tschetter
>            Assignee: Jordan Zimmerman
>         Attachments: CURATOR-21-docs.patch, CURATOR-21-Fix_watcher_race.patch, CURATOR-21.patch
> PathChildrenCache currently takes an Executor, but only to fire off a Runnable that does
a blocking while loop waiting for work.  This means that you must have one thread per PathChildrenCache,
which is not that great.
> PathChildrenCache should just use the Executor's work queuing mechanism to enqueue work
items instead of maintaining its own work queue mechanism.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message