You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2021/07/01 09:15:00 UTC
[jira] [Commented] (IGNITE-15033) AssertionError: Unexpected
rebalance on rebalanced cluster
[ https://issues.apache.org/jira/browse/IGNITE-15033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17372565#comment-17372565 ]
Ignite TC Bot commented on IGNITE-15033:
----------------------------------------
{panel:title=Branch: [pull/9211/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9211/head] Base: [master] : New Tests (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}PDS (Indexing){color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=6067971]]
* {color:#013220}IgnitePdsWithIndexingCoreTestSuite: RestorePartitionStateDuringCheckpointTest.test - PASSED{color}
{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=6067308&buildTypeId=IgniteTests24Java8_RunAll]
> AssertionError: Unexpected rebalance on rebalanced cluster
> ----------------------------------------------------------
>
> Key: IGNITE-15033
> URL: https://issues.apache.org/jira/browse/IGNITE-15033
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There is a low probably that partition state restored incorrectly when a cache is starting with data on disk.
> The issue happened because cluster can save the partition meta page during it state is still restored.
> The code is shown below (GridCacheOffheapManager.java):
> {code:java}
> @Override public Map<Integer, Long> restorePartitionStates {
> //Here the metapage was restored from disk, but it state is not recovery in GridDhtLocalPartition.
> part.dataStore().init();
> ... // Here another thread will be able to execute saveStoreMetadata and set an incorrect state on the metapage.
> //State will be recovered only here.
> long pageAddr = pageMem.writeLock(grp.groupId(), partMetaId, partMetaPage);
> try {
> int stateId = io.getPartitionState(pageAddr);
> updateState(part, stateId);
> }
> finaly {
> pageMem.writeUnlock(grp.groupId(), partMetaId, partMetaPage, null, changed);
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)