Hello! I'm afraid you will have to avoid using visor, use web console instead. The issue should only arise if there are daemon nodes, such as Visor.
Otherwise, if you need node to rejoin cluster & do not mind data, you can remove Ignite work dir in order to start anew. Regards, -- Ilya Kasnacheev вт, 8 янв. 2019 г. в 16:38, radha <[email protected]>: > thanks for the reply. > But currentlly i am working on 2.6.0. It takes some time to move to 2.7.0. > Is there a workaround. > This issue we face when persistence is enabled? > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
