[
https://issues.apache.org/jira/browse/IGNITE-7892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912000#comment-16912000
]
Stanilovsky Evgeny commented on IGNITE-7892:
--------------------------------------------
[~sbberkov] in this case we would have some spaghetti messages, no need to
enable debug logging in high load environment.
> 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
> Priority: Minor
>
> 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
(v8.3.2#803003)
