[
https://issues.apache.org/jira/browse/IGNITE-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-12117:
--------------------------------------
Description:
Test
{{org.apache.ignite.internal.processors.cache.transactions.TxPartitionCounterStateConsistencyTest#testPartitionConsistencyWithBackupsRestart}}
have failure on attempt to handle historical rebalance uging un-striped pool.
You can reproduce it replacing
{noformat}
if (historical) // Can not be reordered.
ctx.kernalContext().getStripedRebalanceExecutorService().execute(r,
Math.abs(nodeId.hashCode()));
{noformat}
with
{noformat}
if (historical) // Can be reordered?
ctx.kernalContext().getRebalanceExecutorService().execute(r);
{noformat}
and yoг will fain following
{noformat}
ava.lang.AssertionError: idle_verify failed on 1 node.
idle_verify check has finished, found 7 conflict partitions:
[counterConflicts=0, hashConflicts=7]
Hash conflicts:
Conflict partition: PartitionKeyV2 [grpId=1544803905, grpName=default,
partId=23]
Partition instances: [PartitionHashRecordV2 [isPrimary=false,
consistentId=nodetransactions.TxPartitionCounterStateConsistencyHistoryRebalanceTest1,
updateCntr=707143, partitionState=OWNING, size=495, partHash=-1503789370],
PartitionHashRecordV2 [isPrimary=false,
consistentId=nodetransactions.TxPartitionCounterStateConsistencyHistoryRebalanceTest2,
updateCntr=707143, partitionState=OWNING, size=494, partHash=-1538739200]]
Conflict partition: PartitionKeyV2 [grpId=1544803905, grpName=default, partId=8]
....
{noformat}
So, we need to investigate reasons and provide proper historical rebalance
refactoring to use the unstriped pool, if possible.
was:
Test
{{org.apache.ignite.internal.processors.cache.transactions.TxPartitionCounterStateConsistencyTest#testPartitionConsistencyWithBackupsRestart}}
have failure on attempt to handle historical rebalance uging un-striped pool.
You can reproduce it replacing
{noformat}
if (historical) // Can not be reordered.
ctx.kernalContext().getStripedRebalanceExecutorService().execute(r,
Math.abs(nodeId.hashCode()));
{noformat}
with
{noformat}
if (historical) // Can be reordered?
ctx.kernalContext().getRebalanceExecutorService().execute(r);
{noformat}
So, we need to investigate reasons and provide proper historical rebalance
refactoring to use the unstriped pool, if possible.
> Historical rebalance should not be processed in striped way
> -----------------------------------------------------------
>
> Key: IGNITE-12117
> URL: https://issues.apache.org/jira/browse/IGNITE-12117
> Project: Ignite
> Issue Type: Task
> Reporter: Anton Vinogradov
> Priority: Major
> Labels: iep-16
>
> Test
> {{org.apache.ignite.internal.processors.cache.transactions.TxPartitionCounterStateConsistencyTest#testPartitionConsistencyWithBackupsRestart}}
> have failure on attempt to handle historical rebalance uging un-striped pool.
> You can reproduce it replacing
> {noformat}
> if (historical) // Can not be reordered.
>
> ctx.kernalContext().getStripedRebalanceExecutorService().execute(r,
> Math.abs(nodeId.hashCode()));
> {noformat}
> with
> {noformat}
> if (historical) // Can be reordered?
> ctx.kernalContext().getRebalanceExecutorService().execute(r);
> {noformat}
> and yoг will fain following
> {noformat}
> ava.lang.AssertionError: idle_verify failed on 1 node.
> idle_verify check has finished, found 7 conflict partitions:
> [counterConflicts=0, hashConflicts=7]
> Hash conflicts:
> Conflict partition: PartitionKeyV2 [grpId=1544803905, grpName=default,
> partId=23]
> Partition instances: [PartitionHashRecordV2 [isPrimary=false,
> consistentId=nodetransactions.TxPartitionCounterStateConsistencyHistoryRebalanceTest1,
> updateCntr=707143, partitionState=OWNING, size=495, partHash=-1503789370],
> PartitionHashRecordV2 [isPrimary=false,
> consistentId=nodetransactions.TxPartitionCounterStateConsistencyHistoryRebalanceTest2,
> updateCntr=707143, partitionState=OWNING, size=494, partHash=-1538739200]]
> Conflict partition: PartitionKeyV2 [grpId=1544803905, grpName=default,
> partId=8]
> ....
> {noformat}
> So, we need to investigate reasons and provide proper historical rebalance
> refactoring to use the unstriped pool, if possible.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
