I've had problems with the visor cache command failing when a client is connected, which was related to TCP port firewalls. Visor was trying to make a connection that was blocked. I don't remember whether top failed.
On Mon, Apr 9, 2018 at 7:10 AM, vbm <[email protected]> wrote: > Hi Dave > > In the ignite pod logs of the server, I see that the cluster is formed. > I see the below trace when I run the command, > [02:53:18] Topology snapshot [ver=4, servers=4, clients=0, CPUs=8, > heap=6.0GB] > > This indicates the cluster of 4 nodes has formed. > > When I login to the container and try to run the ignite visor, it says > connected. But when I tried some commands like top, cache. They were not > returning any result. > > > I got a link in stack overflow on the usage of visor in K8s > https://stackoverflow.com/questions/45197520/running-the- > ignite-visor-in-kubernetes > > So as per this, I created a new pod and as part of docker run command I > gave > the config file for ignite visor. With this it was able to connect to the > cluster. > > Is this the right approach in K8s environment ? If this is correct, how do > I > take care of different input from user to the ignite visor to this pod ? > > > Regards, > Vishwas > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
