Can you check topology in ignite visor console. If you can find the zombie node
there you can kill using kill command in visor.
Regards,
Prem
> On 07-Aug-2018, at 11:01 AM, arunkjn wrote:
>
> Him
>
> It only shows one process each time which is 'grep ignite' the one I am
> running. It does
Him
It only shows one process each time which is 'grep ignite' the one I am
running. It does not list any other ignite process. I have tried this before
as well.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
ps -aef |grep Ignite
Use this command and kill Ignite process
On Tue, Aug 7, 2018, 10:39 AM arunkjn wrote:
> Thanks for the suggestion srecon. I will try that out.
>
> But is there any way I can find out and kill that ignite node? I have tried
> deleting the configured wal and persistance
Thanks for the suggestion srecon. I will try that out.
But is there any way I can find out and kill that ignite node? I have tried
deleting the configured wal and persistance directories. Tried JPS to list
all java processes but could not find any. Even rebooted my system but the
zombie node
Hi,
To avoid this situation, the easiest way to configure static IP instead of
TcpDiscoveryMulticastIpFinder. Use *TcpDiscoveryVmIpFinder* and write down
all the IP address and ports to which you are going to connect. These
particular configuration helps you to protect from the ghost nodes in a
Hi,
I am using ignite 2.5.0 in local development. When I start a server node in
my code, in the logs I can see that 2 server nodes are present in cluster.
[22:10:46] Topology snapshot [ver=80, servers=2, clients=0, CPUs=8,
offheap=4.6GB, heap=4.0GB]
[22:10:46] ^-- Node
