Re: Unable to create cluster of Apache Ignite Server Containers running on individual VMs

I feel you should use "vm.TcpDiscoveryVmIpFinder" instead of cloud. What the error after you use "vm.TcpDiscoveryVmIpFinder"? I am using container based setup using zookeeper based discovery and its working fine. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/U

Failed to find configuration in: file:////tmp/shared.xml

I am using zookeeper based discovery for ignite cluster and ignite nodes are getting properly connected. When i am setting same config.xml file in zeppelin ignite interpreter in , I am not able to run the ignite. it fails with below exception. *It gives me below error on zepplin:* Failed to find

Re: Web Console on Local Machine not working

@Alexey We are eagerly waiting for changes to be pushed and make web console working. Please push frontend and backend folders to master/1.7 branch. Thanks Pavan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Web-Console-on-Local-Machine-not-working-tp7229p758

Re: Web Console on Local Machine not working

Thats great!! Thanks for quick update. And you were supposed to update backend/frontend folder to master as per below reply? (It seems that we forget to push changes to ignite-1.7. I will push all changes to master tomorrow and you will be able to start Web Console from master.) -- View this

Re: Web Console on Local Machine not working

@Alexey Do you know if the changes are pushed. Also any update on docker? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Web-Console-on-Local-Machine-not-working-tp7229p7367.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Web Console on Local Machine not working

I saw your new instructions mentioned on https://cwiki.apache.org/confluence/display/IGNITE/Web+Console. I cant see folders backend and frontend in web-console folder. I have git cloned following directory https://github.com/apache/ignite.git -- View this message in context: http://apache

Re: Web Console on Local Machine not working

That will be awesome man!! Thanks. Though i am installing 1.7. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Web-Console-on-Local-Machine-not-working-tp7229p7259.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Web Console on Local Machine not working

I changed the JSZip version in package.json to 2 and then executed the npm install --no-optional. Node serve started without any errors. with below port number statements: Start listening on port 3000 Start listening on port 3002 Now i executed following command: gulp watch --debug It says serve

Re: Web Console on Local Machine not working

Thanks @andrey for your fast reply. But before moving on to 1.7 i have one question. Node serve itself is failing with error i mentioned, so do you think it should be fixed before moving on to 1.7? Or you feel upgrading directly to 1.7 will resolve it? Thanks in advance. -- View this messa

Web Console on Local Machine not working

Hello, i am new to ignite. I am trying to start web-console but could not got through. I have used below link for making web-console work: https://cwiki.apache.org/confluence/display/IGNITE/Web+Console >From above link, when i am executing "node server" command, i am getting below exception: fir