You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "L-Job (Jira)" <ji...@apache.org> on 2022/01/24 04:40:00 UTC
[jira] [Updated] (CURATOR-629) curator 5.2.0 recipes : client event notify service is single thread
[ https://issues.apache.org/jira/browse/CURATOR-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
L-Job updated CURATOR-629:
--------------------------
Affects Version/s: 5.2.0
> 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
> Assignee: Jordan Zimmerman
> 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.1#820001)