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

Alexander Lapin updated IGNITE-25349:
-------------------------------------
    Description: 
.net tests may fail due to cluster intialization hanging (initialization here 
means nodes startup along with tables creation, etc). In case of failure in 
logs we may seeĀ 
{code:java}
MBean for metric set partition.states.zone.18.table.21 can't be created.
07:01:30     javax.management.InstanceAlreadyExistsException: 
org.apache.ignite:group=metrics,name=partition.states.zone.18.table.21 {code}
that might or might not be related to initialization hanging, but definitively 
should be checked on it's own.

[TC 
link|https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/9125295]

> MBean for metric set <> can't be created. InstanceAlreadyExistsException 
> within .net tests initialization flow
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-25349
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25349
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexander Lapin
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain, ignite-3
>
> .net tests may fail due to cluster intialization hanging (initialization here 
> means nodes startup along with tables creation, etc). In case of failure in 
> logs we may seeĀ 
> {code:java}
> MBean for metric set partition.states.zone.18.table.21 can't be created.
> 07:01:30     javax.management.InstanceAlreadyExistsException: 
> org.apache.ignite:group=metrics,name=partition.states.zone.18.table.21 {code}
> that might or might not be related to initialization hanging, but 
> definitively should be checked on it's own.
> [TC 
> link|https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/9125295]



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

Reply via email to