You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitry Pavlov (Jira)" <ji...@apache.org> on 2022/06/14 15:25:00 UTC

[jira] [Resolved] (IGNITE-9813) Unstable behaviour in GridQueryProcessor#processSchemaOperationLocal. Node stop must be checked

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

Dmitry Pavlov resolved IGNITE-9813.
-----------------------------------
    Release Note: The issue seems to be not actual. Tests passed, resolving as can't reproduce.
      Resolution: Cannot Reproduce

> Unstable behaviour in GridQueryProcessor#processSchemaOperationLocal. Node stop must be checked
> -----------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-9813
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9813
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.6
>            Reporter: Taras Ledkov
>            Assignee: Aleksandr
>            Priority: Major
>              Labels: newbie, stability
>
> The test {{DynamicColumnsAbstractConcurrentSelfTest#testDropColumnCoordinatorChange}} periodically fails with exception {{SchemaOperationException: cache not found}}
> because we don't check the node state at the {{GridQueryProcessor#processSchemaOperationLocal}}. The node's stop must be checked here (e.g. by {{GridQueryProcessor#busyLock}}).



--
This message was sent by Atlassian Jira
(v8.20.7#820007)