[CURATOR-673] Complete BackgroundCallback if curator got closed or exceptions from no-zookeeper world

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.6.0
• Assignee: Kezhu Wang
• Reporter: Kezhu Wang
• Created: 17/May/23 11:41
• Updated: 08/Jun/23 16:33
• Resolved: 08/Jun/23 16:33

Description

Currently, BackgroundCallback has only one method to complete it in success call to zookeeper server. But if curator client got closed during background work, it is possible that there is no call to BackgroundCallback. I think it is better to notify callback in all cases. It is also a keypoint to turn BackgroundCallback to CompletableFuture.

Issue Links

• is a parent of: CURATOR-677 Auxiliary background operations are created with no callbacks from main operations
• is related to: CURATOR-675 AsyncStage could stuck from completion due to framework level error listener
• relates to: CURATOR-529 Sync with inBackground doesnt complete if curator client is closed
• relates to: CURATOR-52 Retry issues with background operations
• links to: GitHub Pull Request #464