You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2023/01/16 09:35:00 UTC

[jira] [Assigned] (IGNITE-18516) Access to several configuration tree in one configuration change clojure is not thread-safe

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

Ivan Bessonov reassigned IGNITE-18516:
--------------------------------------

    Assignee: Ivan Bessonov

> Access to several configuration tree in one configuration change clojure is not thread-safe
> -------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-18516
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18516
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Sergey Uttsel
>            Assignee: Ivan Bessonov
>            Priority: Major
>              Labels: ignite-3
>
> h3. Motivation
> In some cases in a change clojure on one configuration tree we need a thread-safe access to another configuration tree.
> For example:
> {code:java}
> zonesConfiguration.change(zonesChange ->
>     zonesChange.changeDistributionZones(zonesListChange -> {
>         tables = tablesConfiguration.tables();
>         boundTables = //find tables which are bound to the distribution zone;
>         if (boundTables.isEmpty())
>             zonesListChange.delete(zoneName);
> })) {code}
> Now there is no guarantee that list of boundTables is not changed before drop zone.
> h3. Definition of Done
> It is possible to get thread-safe access to several configuration tree in one configuration change clojure.
> Fixed TODO marked by IGNITE-18516.



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