[CURATOR-21] PathChildrenCache consumes an entire thread all the time no matter what

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-incubating
• Fix Version/s: 2.0.1-incubating
• Component/s: Recipes
• Assignee: Jordan Zimmerman
• Reporter: Eric Tschetter
• Created: 24/Apr/13 19:30
• Updated: 06/May/13 18:57
• Resolved: 06/May/13 18:57

Description

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.