[ https://issues.apache.org/jira/browse/IGNITE-17925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628447#comment-17628447 ]
Ignite TC Bot commented on IGNITE-17925: ---------------------------------------- {panel:title=Branch: [pull/10362/head] Base: [master] : Possible Blockers (44)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1} {color:#d04437}Platform .NET (Core Linux){color} [[tests 5|https://ci.ignite.apache.org/viewLog.html?buildId=6892497]] * dll: ContinuousQueryTest.TestIncludeExpiredIsFalseByDefaultAndExpiredEventsAreSkipped - Test has low fail rate in base branch 0,0% and is not flaky * dll: ContinuousQueryTest.TestExpiredEventsAreDeliveredWhenIncludeExpiredIsTrue - Test has low fail rate in base branch 0,0% and is not flaky * dll: ContinuousQueryTest.TestMultipleQueriesMultithreaded - Test has low fail rate in base branch 0,0% and is not flaky * dll: ContinuousQueryTest.TestExceptionInFilterIsLoggedAndFilterIsIgnored - Test has low fail rate in base branch 0,0% and is not flaky * dll: ThickExamplesExternalNodeTest.TestThickExampleWithExternalNode(OptimisticTransaction) - Test has low fail rate in base branch 0,0% and is not flaky {color:#d04437}SPI (Discovery){color} [[tests 20|https://ci.ignite.apache.org/viewLog.html?buildId=6892514]] * IgniteSpiDiscoverySelfTestSuite: TcpClientDiscoverySpiSelfTest.testReconnectSegmentedAfterJoinTimeoutServerFailed - Test has low fail rate in base branch 0,0% and is not flaky * IgniteSpiDiscoverySelfTestSuite: TcpClientDiscoverySpiSelfTest.testClientSegmentation - Test has low fail rate in base branch 0,0% and is not flaky * IgniteSpiDiscoverySelfTestSuite: TcpClientDiscoverySpiSelfTest.testReconnectSegmentedAfterJoinTimeoutNetworkError - Test has low fail rate in base branch 0,0% and is not flaky * IgniteSpiDiscoverySelfTestSuite: TcpClientDiscoverySpiFailureTimeoutSelfTest.testClientSegmentation - Test has low fail rate in base branch 0,0% and is not flaky * IgniteSpiDiscoverySelfTestSuite: TcpClientDiscoverySpiFailureTimeoutSelfTest.testReconnectSegmentedAfterJoinTimeoutNetworkError - Test has low fail rate in base branch 0,0% and is not flaky * IgniteSpiDiscoverySelfTestSuite: TcpClientDiscoverySpiFailureTimeoutSelfTest.testReconnectSegmentedAfterJoinTimeoutServerFailed - Test has low fail rate in base branch 0,0% and is not flaky * IgniteSpiDiscoverySelfTestSuite: TcpDiscoverySslSelfTest.testFailedNodes1 - Test has low fail rate in base branch 0,0% and is not flaky * IgniteSpiDiscoverySelfTestSuite: TcpDiscoverySslSelfTest.testFailedNodes2 - Test has low fail rate in base branch 0,0% and is not flaky * IgniteSpiDiscoverySelfTestSuite: TcpDiscoverySslSelfTest.testFailedNodeRestoreConnection - Test has low fail rate in base branch 0,0% and is not flaky * IgniteSpiDiscoverySelfTestSuite: TcpDiscoverySslSelfTest.testFailedNodes4 - Test has low fail rate in base branch 0,0% and is not flaky * IgniteSpiDiscoverySelfTestSuite: TcpDiscoverySslSelfTest.testFailedNodes5 - Test has low fail rate in base branch 0,0% and is not flaky ... and 9 tests blockers {color:#d04437}Basic 1{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=6892420]] * IgniteBasicTestSuite: IgniteSlowClientDetectionSelfTest.testSlowClient - Test has low fail rate in base branch 0,0% and is not flaky {color:#d04437}Cache 1{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=6892425]] * IgniteRestHandlerTestSuite: RestProtocolStartTest.test - Test has low fail rate in base branch 0,0% and is not flaky {color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 16|https://ci.ignite.apache.org/viewLog.html?buildId=6892525]] * ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testStopNodeOnSegmentaion - Test has low fail rate in base branch 0,0% and is not flaky * ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoveryCommunicationFailureTest.testCommunicationErrorResolve_KillCoordinator_2 - Test has low fail rate in base branch 0,0% and is not flaky * ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoveryCommunicationFailureTest.testCommunicationErrorResolve_KillCoordinator_1 - Test has low fail rate in base branch 0,0% and is not flaky * ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoveryCommunicationFailureTest.testDefaultCommunicationFailureResolver1 - Test has low fail rate in base branch 0,0% and is not flaky * ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoveryCommunicationFailureTest.testCommunicationFailureResolve_KillCoordinator_5 - Test has low fail rate in base branch 0,0% and is not flaky * ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoveryCommunicationFailureTest.testCommunicationErrorResolve_KillCoordinator_4 - Test has low fail rate in base branch 0,0% and is not flaky * ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoveryCommunicationFailureTest.testCommunicationErrorResolve_KillCoordinator_3 - Test has low fail rate in base branch 0,0% and is not flaky * ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoveryCommunicationFailureTest.testCommunicationErrorResolve_KillNode_2 - Test has low fail rate in base branch 0,0% and is not flaky * ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoveryCommunicationFailureTest.testCommunicationErrorResolve_KillNode_1 - Test has low fail rate in base branch 0,0% and is not flaky * ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoveryCommunicationFailureTest.testDefaultCommunicationFailureResolver5 - Test has low fail rate in base branch 0,0% and is not flaky * ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoveryCommunicationFailureTest.testDefaultCommunicationFailureResolver4 - Test has low fail rate in base branch 0,0% and is not flaky ... and 5 tests blockers {color:#d04437}Web Sessions{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=6892522]] {panel} {panel:title=Branch: [pull/10362/head] Base: [master] : New Tests (2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1} {color:#00008b}SPI (Discovery){color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=6892514]] * {color:#013220}IgniteSpiDiscoverySelfTestSuite: TcpDiscoverySegmentationPolicyTest.testDefaultPolicy - PASSED{color} {color:#00008b}JDBC Driver{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=6892475]] * {color:#013220}IgniteJdbcDriverTestSuite: JdbcThinMetadataSelfTest.testIndexMetadataMatchesSystemView - PASSED{color} {panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=6892530&buildTypeId=IgniteTests24Java8_RunAll] > Ability to use configured FailureHandler for segmentation handling > ------------------------------------------------------------------ > > Key: IGNITE-17925 > URL: https://issues.apache.org/jira/browse/IGNITE-17925 > Project: Ignite > Issue Type: Task > Reporter: Ilya Shishkov > Assignee: Ilya Shishkov > Priority: Minor > Labels: ise > Time Spent: 10m > Remaining Estimate: 0h > > Now, we have 3 possible ways to process segmentation by means of > {{{}SegmentationPolicy{}}}: > # Stop segmented node - {{SegmentationPolicy#STOP}} > # Restart segmented node - {{SegmentationPolicy#RESTART_JVM}} > # Do nothing - {{SegmentationPolicy#NOOP}} > Under the hood, behavior of segmentation handling (i.e. failure handling) is > overridden [1, 2]. > For example, instead of using {{StopNodeOrHaltFailureHandler}} configured by > default, default segmentation handling will use {{StopNodeFailureHandler}} > which can hang during stop process. > As a solution, we can add extra {{SegmentationPolicy#USE_FAILURE_HANDLER}} > which will be used by default. > Links: > # > [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/managers/discovery/GridDiscoveryManager.java#L3300] > # > [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/managers/discovery/GridDiscoveryManager.java#L2983] -- This message was sent by Atlassian Jira (v8.20.10#820010)