You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Denis Chudov (Jira)" <ji...@apache.org> on 2023/07/26 10:01:00 UTC

[jira] [Assigned] (IGNITE-20053) Empty data nodes are returned by data nodes engine

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

Denis Chudov reassigned IGNITE-20053:
-------------------------------------

    Assignee: Denis Chudov

> Empty data nodes are returned by data nodes engine
> --------------------------------------------------
>
>                 Key: IGNITE-20053
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20053
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Chudov
>            Assignee: Denis Chudov
>            Priority: Major
>              Labels: ignite-3
>
> There is a meta storage key called DISTRIBUTION_ZONES_LOGICAL_TOPOLOGY_KEY and it is refreshed by topology listener on topology events and stores logical topology. If the value stored by this key is null, then empty data nodes are returned from data nodes engine on data nodes calculation for a distribution zone. As a result, empty assignments are calculated for partitions, which leads to exception described in IGNITE-19466.
> Some integration tests, for example, ItRebalanceDistributedTest are flaky because of possible problems with value of DISTRIBUTION_ZONES_LOGICAL_TOPOLOGY_KEY and empty data nodes calculated by data nodes engine.
> Actually, the empty data nodes collection is a wrong result for this case because the current logical topology is not empty.



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