You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Pavel Kovalenko (JIRA)" <ji...@apache.org> on 2018/12/20 19:40:00 UTC
[jira] [Created] (IGNITE-10771) Print troubleshooting hint when
exchange latch got stucked
Pavel Kovalenko created IGNITE-10771:
----------------------------------------
Summary: Print troubleshooting hint when exchange latch got stucked
Key: IGNITE-10771
URL: https://issues.apache.org/jira/browse/IGNITE-10771
Project: Ignite
Issue Type: Improvement
Components: cache
Affects Versions: 2.5
Reporter: Pavel Kovalenko
Fix For: 2.8
Sometimes users face with a problem when exchange latch can't be completed:
{noformat}
2018-12-12 07:07:57:563 [exchange-worker-#42] WARN
o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture:488 - Unable to await
partitions release latch within timeout: ClientLatch
[coordinator=ZookeeperClusterNode [id=6b9fc6e4-5b6a-4a98-be4d-6bc1aa5c014c,
addrs=[172.17.0.1, 10.0.230.117, 0:0:0:0:0:0:0:1%lo, 127.0.0.1], order=3,
loc=false, client=false], ackSent=true, super=CompletableLatch [id=exchange,
topVer=AffinityTopologyVersion [topVer=45, minorTopVer=1]]]
{noformat}
It may indicate that some node in a cluster can' t finish partitions release (finish all ongoing operations at the previous topology version) or it can be silent network problem.
We should print to log a hint how to troubleshoot it to reduce the number of questions about such problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)