[
https://issues.apache.org/jira/browse/CURATOR-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kezhu Wang closed CURATOR-629.
------------------------------
Assignee: (was: Jordan Zimmerman)
Resolution: Not A Problem
Most framework uses single thread to execute callbacks to maintain ordered
delivery. Curator and ZooKeeper have no exception.
> curator 5.2.0 recipes : client event notify service is single thread
> --------------------------------------------------------------------
>
> Key: CURATOR-629
> URL: https://issues.apache.org/jira/browse/CURATOR-629
> Project: Apache Curator
> Issue Type: Improvement
> Affects Versions: 5.2.0
> Reporter: L-Job
> Priority: Major
>
> when I try to create a new node in zookeeper in a event, to trigger another
> event. The original event takes a long time to end , and then find the new
> event what I expected is never hadppend.
> I found the thread[NotifyService-0] is only thread when client try to notify
> the event happended, I think this is not the elegant way to notify
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
