Description
When writing data to ZooKeeper via Curator, I found that when I was receiving a KeeperException NoAuth back from ZooKeeper, my call would hang indefinitely.
The NoAuth was expected as I was testing writing to a path where the ACL was set to prevent my client from writing (X509 authentication scheme).
The call which hangs:
myFramework.set(myModel).toCompletableFuture().get();
The logs from the call:
2023-03-29 14:20:29,511 [Curator-Framework-0] ERROR imps.CuratorFrameworkImpl - Background exception was not retry-able or retry gave up
org.apache.zookeeper.KeeperException$NoAuthException: KeeperErrorCode = NoAuth for /test/foo
I'd expect this exception to bubble up wrapped in a CompletionException.
Instead, CuratorFrameworkImpl just logs the exception and then the call to get() hangs indefinitely.
Attachments
Issue Links
- links to