I have noticed that retry-able errors (CONNECTIONLOSS, OPERATIONTIMEOUT, SESSIONMOVED, SESSIONEXPIRED) are not propagated to callback when the retry policy gave up if the operation is done in background.
It is a little bit confusing because it is not the behavior of the Zookeeper client. Check the 2 test cases here : https://gist.github.com/barkbay/6411061 Would you mind if i open a JIRA with the following patch : https://github.com/barkbay/incubator-curator/commit/c58d4d8e76ee12137092d95c1ef33d4fa85e5aea#curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
