[
https://issues.apache.org/jira/browse/IGNITE-23445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Chesnokov updated IGNITE-23445:
-----------------------------------------
Description:
The {{CacheGroupMetricsImpl.onTopologyInitialized}} method completes execution
even when {{ctx.topology().initialized()}} returns {{{}false{}}}. This leads to
the execution of logic that depends on an initialized topology, potentially
causing unexpected errors in the system.
{*}Steps to Reproduce{*}:
# Run testClientNodePds.
# See result of {{ctx.topology().initialized()}} in
{{CacheGroupMetricsImpl.onTopologyInitialized}} method. It return false now,
but must be true
For more details watch issue links
was:
The {{CacheGroupMetricsImpl.onTopologyInitialized}} method completes execution
even when {{topology.initialized()}} returns {{{}false{}}}. This leads to the
execution of logic that depends on an initialized topology, potentially causing
unexpected errors in the system.
{*}Steps to Reproduce{*}:
# Run testClientNodePds.
# See result of ctx.topology().initialized() in
{{CacheGroupMetricsImpl.onTopologyInitialized}} method. It return false now,
but must be true
For more details watch issue links
> onTopologyInitialized method works with not initialized topology
> ----------------------------------------------------------------
>
> Key: IGNITE-23445
> URL: https://issues.apache.org/jira/browse/IGNITE-23445
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Aleksandr Chesnokov
> Priority: Minor
>
> The {{CacheGroupMetricsImpl.onTopologyInitialized}} method completes
> execution even when {{ctx.topology().initialized()}} returns {{{}false{}}}.
> This leads to the execution of logic that depends on an initialized topology,
> potentially causing unexpected errors in the system.
> {*}Steps to Reproduce{*}:
> # Run testClientNodePds.
> # See result of {{ctx.topology().initialized()}} in
> {{CacheGroupMetricsImpl.onTopologyInitialized}} method. It return false now,
> but must be true
> For more details watch issue links
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
