Remote node gc pause

[Ignitebie <an...@gmail.com>]

Hi,

We see following error in our grid quite frequently. 


2016-09-09 09:36:12.458 BST [WARN] -
thread="tcp-disco-msg-worker-#2%MMEventOrchestratorGrid%" -
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi" - Timed out
waiting for message to be read (most probably, the reason is in long GC
pauses on remote node) [curTimeout=20000]

What is missing in this are the details about remote node (id/host/port).

Is there a configuration to see (I believe if it is trying to connect and
timeout, then it also knows which node that is) those details so that one
can go and instantly check memory status. For larger grid, checking logs and
memory status for each remote node is difficult.

Thanks.





--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Remote-node-gc-pause-tp7632.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Remote node gc pause

[Anmol Rattan <an...@gmail.com>]

Created one for same.

https://issues.apache.org/jira/browse/IGNITE-3898


Thanks & Regards
Anmol Rattan
+91 9538901262


On Fri, Sep 9, 2016 at 11:04 PM, vkulichenko <va...@gmail.com>
wrote:

> Hi,
>
> I agree. Can you create a JIRA ticket for this?
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Remote-node-gc-pause-tp7632p7641.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Remote node gc pause

[vkulichenko <va...@gmail.com>]

Hi,

I agree. Can you create a JIRA ticket for this?

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Remote-node-gc-pause-tp7632p7641.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.