[
https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022023#comment-17022023
]
Ignite TC Bot commented on IGNITE-12227:
----------------------------------------
{panel:title=Branch: [pull/7278/head] Base: [ignite-2.8] : Possible Blockers
(13)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4947339]]
* IgniteCacheTestSuite6:
TxRollbackOnMapOnInvalidTopologyTest.testRollbackOnMapToInvalidTopology_1 -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}MVCC PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4946735]]
* IgnitePdsMvccTestSuite2:
WalDeletionArchiveFsyncTest.testCorrectDeletedArchivedWalFiles - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=4946664]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoveryConcurrentStartAndStartStopTest.testStartStop1 - 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
{color:#d04437}Platform .NET (Long Running){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4946715]]
* exe: 0",2).TestServerSideExpiryPolicyWorksOnAllVersions - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 5{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=4947341]]
* IgniteCacheTestSuite5:
CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClientsNodeRestart
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
CacheSerializableTransactionsTest.testConflictResolution - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
CacheSerializableTransactionsTest.testNoOptimisticExceptionOnChangingTopology -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
CacheSerializableTransactionsTest.testIncrementTxRestart - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 7{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=4946696]]
* IgniteCacheTestSuite7:
AuthenticationProcessorNodeRestartTest.testConcurrentAddUpdateRemoveNodeRestartServer
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite7:
AuthenticationProcessorNodeRestartTest.testConcurrentAuthorize - Test has low
fail rate in base branch 0,0% and is not flaky
{color:#d04437}MVCC Cache{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4946673]]
* IgniteCacheMvccTestSuite:
DataStreamProcessorMvccPersistenceSelfTest.testTryFlush - Test has low fail
rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4946741&buildTypeId=IgniteTests24Java8_RunAll]
> Default auto-adjust baseline enabled flag calculated incorrectly in some cases
> ------------------------------------------------------------------------------
>
> Key: IGNITE-12227
> URL: https://issues.apache.org/jira/browse/IGNITE-12227
> Project: Ignite
> Issue Type: Bug
> Reporter: Anton Kalashnikov
> Assignee: Anton Kalashnikov
> Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> baselineAutoAdjustEnabled can be been different on different nodes because of
> the calculation of default value happening locally on each node and including
> only local configuration. It issue can happen by the following reasons:
> * If IGNITE_BASELINE_AUTO_ADJUST_ENABLED flag set to a different value on
> different nodes it leads to cluster hanging due to baseline calculation
> finishing with the unpredictable state on each node.
> * if cluster in mixed mode(included in-memory and persistent nodes) sometimes
> flag is set to a different value due to calculation doesn't consider remote
> nodes configuration.
> Possible solution(both points required):
> * Get rid of IGNITE_BASELINE_AUTO_ADJUST_ENABLED and replace it by the
> explicit call of IgniteCluster#baselineAutoAdjustEnabled where it
> required(test only).
> * Calculating default value on the first started node as early as
> possible(instead of activation) and this value always should be set to
> distributed metastorage(unlike it happening now). It means that instead of
> awaiting activation, the default value would be calculated by the first
> started node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
