ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Muzafarov (Jira)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-12117) Historical rebalance should NOT be processed in striped way
Date Thu, 10 Oct 2019 11:35:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maxim Muzafarov updated IGNITE-12117:
-------------------------------------
    Fix Version/s:     (was: 2.8)
                   2.9

> 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
>             Fix For: 2.9
>
>
> Test {{org.apache.ignite.internal.processors.cache.transactions.TxPartitionCounterStateConsistencyTest#testPartitionConsistencyWithBackupsRestart}}
have failure on attempt to handle historical rebalance using un-striped pool.
> You can reproduce it by 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 you will gain the 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.4#803005)

Mime
View raw message