[
https://issues.apache.org/jira/browse/IGNITE-23837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903089#comment-17903089
]
Vladislav Pyatkov commented on IGNITE-23837:
--------------------------------------------
Also, we decided to increase the default lock slots to 1M (currently it is
130K).
> Add log when lock manager run out of slots
> ------------------------------------------
>
> Key: IGNITE-23837
> URL: https://issues.apache.org/jira/browse/IGNITE-23837
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3.Motivation
> Lock manager uses some limited slot to increase a searching state by the key.
> When the amount of slots is exhausted, the lock state becomes shared. Hence,
> several different lock keys might have a conflict.
> The states start sharing only in case of a high load of the node. The lock
> conflict exceptions look unexpected without additional information.
> h3.Definition of done
> * Output periodic information about the lock states if the states were
> starting to be shared.
> * Consider the ability to add information about whether the lock state is
> shared.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
