Suggested logging settings to debug disconnects?

[Ryan Ripken <ry...@rmanet.com>]

I'm using TcpDiscovery with the nodes running at Amazon.  So far the 
networking inside the Amazon cloud has been rock solid.  That said, over 
the weekend I had two compute tasks fail because of an empty 
projection.  It looks like the compute nodes all disconnected.

Its unclear why exactly the nodes disconnected.

I'm thinking of increasing the number of missed heartbeats but I'd also 
like to increase the amount of logging so that I have more information 
to debug similar errors in the future.

I know that Ignite logging can be verbose - does anyone have suggestions 
for how I'd want to configure the logging in order to capture clues to 
diagnose the random disconnects but also not have a mountain of useless 
logs?

Thanks!
Ryan

Re: Suggested logging settings to debug disconnects?

[Evgenii Zhuravlev <e....@gmail.com>]

Hi,

You can turn on Debug logging for packages by configuring
%IGNITE_HOME%/config/ignite-log4j.xml,


For example, you can add

<category name="org.apache.ignite.spi">

    <level value="DEBUG"/>
</category>

to see DEBUG logs from both Discovery & Communication, or at least,


<category name="org.apache.ignite.spi.discovery">
    <level value="DEBUG"/>
</category>

for DEBUG logs only from Discovery.

Evgenii


2017-05-31 20:56 GMT+03:00 Ryan Ripken <ry...@rmanet.com>:

> I'm using TcpDiscovery with the nodes running at Amazon.  So far the
> networking inside the Amazon cloud has been rock solid.  That said, over
> the weekend I had two compute tasks fail because of an empty projection.
> It looks like the compute nodes all disconnected.
>
> Its unclear why exactly the nodes disconnected.
>
> I'm thinking of increasing the number of missed heartbeats but I'd also
> like to increase the amount of logging so that I have more information to
> debug similar errors in the future.
>
> I know that Ignite logging can be verbose - does anyone have suggestions
> for how I'd want to configure the logging in order to capture clues to
> diagnose the random disconnects but also not have a mountain of useless
> logs?
>
> Thanks!
> Ryan
>