[ https://issues.apache.org/jira/browse/ZOOKEEPER-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamas Penzes updated ZOOKEEPER-2586: ------------------------------------ Labels: remove_watches (was: ) > zoo_aremove_watchers() does not remove a watch of path has more than one watch > ------------------------------------------------------------------------------ > > Key: ZOOKEEPER-2586 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2586 > Project: ZooKeeper > Issue Type: Bug > Reporter: prashant > Priority: Major > Labels: remove_watches > > three issues > 1)zoo_aremove_watchers() does not remove a watch if path has more than one > watch. > but it works in below cases. > it removes watch if path has only one watch. > and it removes all watches if watcher function arguments is NULL. > Seen in > zookeeper.version=3.5.1-alpha--1, built on 06/09/2016 18:31 GMT > Not sure if this is fixed in later versions. > 2) If zoo_aremove_watchers() is called with local=1, then client hangs in > waiting for mutex in mt_adaptor.c:102 > void notify_sync_completion(struct sync_completion *sc) > { > pthread_mutex_lock(&sc->lock); > ... > 3) Acts like sync API if no node and no watcher on path. > it does not call async completion callback in this case. -- This message was sent by Atlassian JIRA (v7.6.3#76005)