This issue once reproduced in my productive with similar stack trace. During
sources analysis I saw the use unsafe of method
writeLock().isHeldByCurrentThread() for unlocking checkpoint. This may cause
thread to starvation. Problem no longer appeared after local fix.
I prepared pull request https://github.com/apache/ignite/pull/7445. 
Accept please jira issue to me and review my PR.




--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Reply via email to