You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2016/02/23 02:36:18 UTC
[jira] [Created] (IGNITE-2709) High contention on a cache key leads
to high thread stack usage
Alexey Goncharuk created IGNITE-2709:
----------------------------------------
Summary: High contention on a cache key leads to high thread stack usage
Key: IGNITE-2709
URL: https://issues.apache.org/jira/browse/IGNITE-2709
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: ignite-1.4
Reporter: Alexey Goncharuk
Currently {{GridCacheMvccManager#onOwnerChanged}} callback notifies listeners synchronously. This means that the call stack size for a transaction commit is proportional to the size of MVCC candidates queue. On a big enough queue size this leads to a StackOverflowError (see the file attached).
I suggest the {{GridCacheMvccManager:158}} line be executed asynchronously after some (3-5) nested calls.
The change should be properly benchmarked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)