[CURATOR-677] Auxiliary background operations are created with no callbacks from main operations

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.0
• Fix Version/s: 5.6.0
• Assignee: Kezhu Wang
• Reporter: Kezhu Wang
• Created: 05/Jun/23 12:13
• Updated: 03/Sep/23 11:34
• Resolved: 03/Sep/23 11:34

Description

Some of our background operations use auxiliary background operations to complete task in case of primary conditions are not satisfied. But these auxiliary background operations are created with no callbacks from main operations. So in case of closing, background exceptions and retriable errors, these are either abandoned or treated as no callback background operations. Currently, there are three operations which have auxiliary background operations. They are CreateBuilderImpl, DeleteBuilderImpl and SetDataBuilderImpl.

This should be part of CURATOR-673, but I think all these three could be fixed using same pattern. And I want to keep #464 simple.

Issue Links

• is a child of: CURATOR-673 Complete BackgroundCallback if curator got closed or exceptions from no-zookeeper world
• links to: GitHub Pull Request #467