Re: WebConsole does not see cluster

2018-08-14 Thread Alexey Kuznetsov
Hi, KJQ! You will need ignite-rest-http module in class path for those nodes that you are planning to use as gateways for Web Console. Having only one node will means that if this single node goes down - you will lose connection to cluster from Web Console. You may have several agents running an

Re: WebConsole does not see cluster

2018-08-13 Thread KJQ
So, I finally got this working. I ended up: - Copying the rest-http module into my main Ignite node (the only one who's IP i am using for discovery right now). - I shell into the running "ignite" instance and run the web agent from there (not outside the containers) Questions: - I see in "cache

Re: WebConsole does not see cluster

2018-08-12 Thread KJQ
All right, im completely confused at this point. Trying to follow this thread: http://apache-ignite-users.70518.x6.nabble.com/Agent-not-able-to-connect-tt21714.html#a21745 *I see this in the console

WebConsole does not see cluster

2018-08-12 Thread KJQ
Hello. I am trying to get the Dockerized WebConsole running but no matter what I do it does not recognize any clusters. I am running the Web Agent from one of my nodes with the REST (maven) dependencies. I can see the nodes coming up when I start my services and using the CLI I can inspect the