You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexander Belyak (JIRA)" <ji...@apache.org> on 2018/03/06 15:01:00 UTC

[jira] [Created] (IGNITE-7892) Remove aquirence of any locks from toString methods

Alexander Belyak created IGNITE-7892:
----------------------------------------

             Summary: Remove aquirence of any locks from toString methods
                 Key: IGNITE-7892
                 URL: https://issues.apache.org/jira/browse/IGNITE-7892
             Project: Ignite
          Issue Type: Wish
          Components: general
    Affects Versions: 2.4
            Reporter: Alexander Belyak


In org.apache.ignite.internal.processors.cache.GridCacheMapEntry we have thread safe toString() method that can lead to some hangs of monitoring threads like grid-timeout-worker if we try to dump LongRunningOperations with locked entry.
I think that toString methods will never need to be a thread safe and can throw ConcurrentModificationException or print inconsistent data, so we must remove synchronization from every toString methods in codebase. If we need some "consistent" string representation - let's add consistentToString methods or do external synchronization.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)