[
https://issues.apache.org/jira/browse/IGNITE-24048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov resolved IGNITE-24048.
----------------------------------------
Fix Version/s: 3.0
Resolution: Fixed
> TablePartitionId's hash might lead to collisions in HeapLockManager
> -------------------------------------------------------------------
>
> Key: IGNITE-24048
> URL: https://issues.apache.org/jira/browse/IGNITE-24048
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Current implementation simply does {{{}tableId ^ partId{}}}, which will lead
> to full hash collisions if we have different tables with close enough IDs. As
> a result, we will have a higher contention between independent transactions.
> We should use another hash function with a better distributions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)