You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2023/10/24 07:23:00 UTC

[jira] [Updated] (IGNITE-20624) Sql. Race between getting logical topology and mapping fragments

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

Konstantin Orlov updated IGNITE-20624:
--------------------------------------
    Summary: Sql. Race between getting logical topology and mapping fragments  (was: Race between getting logical topology and mapping fragments)

> Sql. Race between getting logical topology and mapping fragments
> ----------------------------------------------------------------
>
>                 Key: IGNITE-20624
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20624
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Roman Puchkovskiy
>            Assignee: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> MappingServiceImpl#nodesSetRef might contain an empty set when mapping if the logical topology event hasn't occurred yet. This results in colocation targets having {{nodes}} equal to 0, so no targets are colocated, even if they are supposed to be. This results in 'ColocationMappingException: Targets are not colocated' (thrown in AbstractTarget:123, as of commit b9bd1c4db01a5377190b363c208375d845890265).
> This is easily reproducible locally with ItDataSchemaSyncTest#checkSchemasCorrectlyRestore()



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