[jira] [Assigned] (CURATOR-677) Auxiliary background operations are created with no callbacks from main operations

["Kezhu Wang (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CURATOR-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kezhu Wang reassigned CURATOR-677:
----------------------------------

    Assignee: Kezhu Wang  (was: Enrico Olivelli)

> Auxiliary background operations are created with no callbacks from main operations
> ----------------------------------------------------------------------------------
>
>                 Key: CURATOR-677
>                 URL: https://issues.apache.org/jira/browse/CURATOR-677
>             Project: Apache Curator
>          Issue Type: Bug
>    Affects Versions: 5.5.0
>            Reporter: Kezhu Wang
>            Assignee: Kezhu Wang
>            Priority: Major
>             Fix For: 5.6.0
>
>
> 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|https://github.com/apache/curator/pull/464] simple.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)