[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[ https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025951#comment-17025951 ] Maxim Muzafarov commented on IGNITE-12227: -- It seems the same tests have been affected by the initial PR too [pull/7150/head] (before merge to master) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5810373459874129800=testDetails_IgniteTests24Java8=pull%2F7150%2Fhead > 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: 40m > 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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[ https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025914#comment-17025914 ] Maxim Muzafarov commented on IGNITE-12227: -- It seems to me we've got flaky failures here due to these changes. https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache5_IgniteTests24Java8=ignite-2.8=buildTypeStatusDiv > 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: 40m > 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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[ https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022238#comment-17022238 ] Maxim Muzafarov commented on IGNITE-12227: -- cherry-picked to 2.8 > 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: 40m > 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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[
https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1708#comment-1708
]
Ignite TC Bot commented on IGNITE-12227:
{panel:title=Branch: [pull/7278/head] Base: [ignite-2.8] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4946741buildTypeId=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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[
https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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=4946741buildTypeId=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
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[
https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022003#comment-17022003
]
Ignite TC Bot commented on IGNITE-12227:
{panel:title=Branch: [pull/7278/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Continuous Query 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=4952946]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryFailoverAtomicNearEnabledSelfSelfTest.testMultiThreadedFailover
- New test duration 63s is more that 1 minute
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousQueryFailoverAtomicNearEnabledSelfSelfTest.testFailoverStartStopBackup
- New test duration 64s is more that 1 minute
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4946741buildTypeId=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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[ https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17020174#comment-17020174 ] Maxim Muzafarov commented on IGNITE-12227: -- [~akalashnikov], [~agoncharuk] PR to ignite-2.8 branch created. TC started. https://github.com/apache/ignite/pull/7278 > 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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[ https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019374#comment-17019374 ] Alexey Goncharuk commented on IGNITE-12227: --- Looks good to me as well, merged to master. [~mmuzaf], can you cherry-pick the commit to ignite-2.8? > 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: 20m > 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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[ https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019353#comment-17019353 ] Ivan Bessonov commented on IGNITE-12227: [~akalashnikov] looks good, let's merge it. I hope that there were no new tests with that property in last few days. > 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: 10m > 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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[
https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018135#comment-17018135
]
Ignite TC Bot commented on IGNITE-12227:
{panel:title=Branch: [pull/7150/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4938318buildTypeId=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: 10m
> 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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[ https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016126#comment-17016126 ] Anton Kalashnikov commented on IGNITE-12227: [~mmuzaf], Unfortunately, these changes found the bug in discovery and I had stuck on the investigation of this problem for a while. But looks like I've understood the issue and I have some solution. I believe I'll extract this problem to another ticket because it's not simple changes. And I hope in the nearest time I'll finish this task. > 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: 10m > 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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[ https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014202#comment-17014202 ] Maxim Muzafarov commented on IGNITE-12227: -- [~akalashnikov] Hello, any updates over this issue? > 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: 10m > 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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[ https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998240#comment-16998240 ] Anton Kalashnikov commented on IGNITE-12227: [~mmuzaf] It's almost finished. I'm just waiting for the tests finishing. > 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: 10m > 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)
[jira] [Commented] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases
[ https://issues.apache.org/jira/browse/IGNITE-12227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985148#comment-16985148 ] Maxim Muzafarov commented on IGNITE-12227: -- [~akalashnikov] Hello! Are you still working on this issue? Any updates? > 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 > > > 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)
