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 and configured to communicate with different nodes. See node-uri option in Web Agent "README.txt" Or starting from Ignite 2.7 (already in master, but was not released yet) you may specify several cluster nodes URIs as comma separated string. >- I see in "caches" my cache. Should I see my configurations in > configurations as well or is that only for created ones? It is not clear for me what did you mean. Can you attach a screenshot with example? On Tue, Aug 14, 2018 at 1:32 AM KJQ <[email protected]> wrote: > 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 "caches" my cache. Should I see my configurations in > configurations as well or is that only for created ones? > > - Where do I need the agent and rest api? It seems like having it in the > one node will suffice. Do I need to have both on every node? > > > > ----- > KJQ > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > > -- > Alexey Kuznetsov > <http://apache-ignite-users.70518.x6.nabble.com/> >
