Hello! I think that Visor will talk to all nodes when trying to run caches command, and if it can't reach client nodes the operation will never finish.
Regards, -- Ilya Kasnacheev ср, 5 июн. 2019 г. в 22:34, John Smith <[email protected]>: > Hi, any thoughts on this? > > On Fri, 31 May 2019 at 10:21, John Smith <[email protected]> wrote: > >> I think it should at least time out and show stats of the nodes it could >> reach? I don't see why it's dependant on client nodes. >> >> On Thu, 30 May 2019 at 11:58, John Smith <[email protected]> wrote: >> >>> Sorry pressed enter to quickly.... >>> >>> So basically I'm 100% sure if visor cache command cannot reach the >>> client node then it just stays there not doing anything. >>> >>> On Thu, 30 May 2019 at 11:57, John Smith <[email protected]> wrote: >>> >>>> Hi, running 2.7.0 >>>> >>>> - I have a 4 node cluster and it seems to be running ok. >>>> - I have clients connecting and doing what they need to do. >>>> - The clients are set as client = true. >>>> - The clients are also connecting from various parts of the network. >>>> >>>> The problem with ignite visor cache command is if visor cannot reach a >>>> specific client node it just seems to hang indefinitely. >>>> >>>> Choose node number ('c' to cancel) [0]: c >>>> visor> cache >>>> >>>> It just stays like that no errors printed nothing... >>>> >>>
