If in topology contains only two nodes, need to view logs from both. A pause can occur as a single node and the second. Please collect log from both nodes and attach files to the topic.
[1] https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-detailed-garbage-collection-stats On Fri, Aug 5, 2016 at 4:58 PM, yucigou <[email protected]> wrote: > Thanks for your reply. Indeed the CPU and memory was a bit intense during > the > period of time when I ran the Apache Ignite Web Console Agent, so as to use > the Apache Ignite Web Console to monitoring my Ignite nodes. But it seemed > under control (notes: figures below are provided by JavaMelody): > <http://apache-ignite-users.70518.x6.nabble.com/file/n6802/usedMemory.png> > <http://apache-ignite-users.70518.x6.nabble.com/file/n6802/cpu.png> > Also the garbage collector time was minimal: > <http://apache-ignite-users.70518.x6.nabble.com/file/n6802/gc.png> > Could there be something wrong caused by the Apache Ignite Web Console > Agent? Or any other possibilities? > > Cheers, > Yuci > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Local-node-seems-to-be-disconnected- > from-topology-failure-detection-timeout-is-reached-tp6797p6802.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
