[jira] [Assigned] (IGNITE-19316) ClusterConfigRegistryImpl should update its internal state

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

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

Aleksandr reassigned IGNITE-19316:
----------------------------------

    Assignee: Aleksandr

> ClusterConfigRegistryImpl should update its internal state
> ----------------------------------------------------------
>
>                 Key: IGNITE-19316
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19316
>             Project: Ignite
>          Issue Type: Bug
>          Components: cli
>            Reporter: Aleksandr
>            Assignee: Aleksandr
>            Priority: Major
>              Labels: ignite-3
>
> ItIgnitePicocliCommandsTest.clusterConfigShowSuggested is flaky because ClusterConfigRegistryImpl returns an empty config. Probably, we have to log exceptions if the onConnect method. At least, we will know why it is happening.
> Also, I would like to add some robust code that will try to update the internal config instance if it is empty.
>  
> {code:java}
> org.awaitility.core.ConditionTimeoutException: Condition with alias 'For given parsed words: [cluster, config, show,  --node-name, nodeName, ]' didn't complete within 10 seconds because lambda expression in org.apache.ignite.internal.cli.core.repl.executor.ItIgnitePicocliCommandsTest: expected iterable with items ["aimem", "aipersist", "metrics", "rocksDb", "table", "zone", "security", "schemaSync"] in any order but no item matches: "aimem", "aipersist", "metrics", "rocksDb", "table", "zone", "security", "schemaSync" in [].
>           at app//org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
> {code}



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