Yeah so far it works great inside DC/OS with marathon.
On Tue, 15 Jan 2019 at 08:01, Ilya Kasnacheev
wrote:
> Hello!
>
> I think there were people on userlist who was able to open Dockerized
> Ignite cluster to outside clients. I recommend searching archives.
>
> Regards,
> --
> Ilya Kasnacheev
Hello!
I think there were people on userlist who was able to open Dockerized
Ignite cluster to outside clients. I recommend searching archives.
Regards,
--
Ilya Kasnacheev
пн, 14 янв. 2019 г. в 21:54, John Smith :
> So if it's all running inside DC/OS it works ni issues. So wondering what
>
So if it's all running inside DC/OS it works ni issues. So wondering what
would be the strategy if external clients want to connect either Ignite
being inside the contaimer env or outside... Just REST?
On Fri., Jan. 11, 2019, 15:00 John Smith Yeah this doesn't work on the dev environment either,
Yeah this doesn't work on the dev environment either, because the
application is running in docker on bridge mode, but the cluster is on
standard VM hosts. I'm using DC/OS...
Does the Mesos deployment support DC/OS? If not I can create custom
marathon docker images for it...
On Fri, 11 Jan 2019
And it seems to say like that indefinitely. I let it go for 5 minutes and
nothing has printed to the console or logs.
On Fri, 11 Jan 2019 at 12:49, John Smith wrote:
> I can confirm I just tested it. There is no stack trace. Basically the
> client connects, no errors, the cache command
That's the thing... There is none. It just seems to pause and wait. The
moment I close my client application it just resumes...
But other commands like top work fine...
On Fri, 11 Jan 2019 at 12:15, Ilya Kasnacheev
wrote:
> Hello!
>
> If they're on the same network it is not obvious what
Hello!
If they're on the same network it is not obvious what happens here, but I
have just performed the steps you have mentioned without problems.
Can you collect stack traces from all nodes when this hang happens?
Regards,
--
Ilya Kasnacheev
пт, 11 янв. 2019 г. в 20:12, Ilya Kasnacheev :
Hello!
I'm afraid that visor will try to connect to your client and will wait
until this is successful.
Regards,
--
Ilya Kasnacheev
пт, 11 янв. 2019 г. в 20:01, John Smith :
> Humm maybe not. The client is running on my laptop through the wi-fi. But
> the cluster and visor are on the dev
Humm maybe not. The client is running on my laptop through the wi-fi. But
the cluster and visor are on the dev network. But the client on my laptop
is capable of joining the cluster through the wi-fi and processing requests
no problems.
On Fri, 11 Jan 2019 at 10:56, Ilya Kasnacheev
wrote:
>
Hello!
Are you sure that your Visor node is able to connect to client node via
communication port? Nodes in cluster need to be able to do that, which is
somewhat unexpected in case of client node.
Regards,
--
Ilya Kasnacheev
пт, 11 янв. 2019 г. в 18:36, John Smith :
> Hi, sorry if this a
Hi, sorry if this a double post I tried through nabble and I don't think it
came through...
So using 2.7...
I have a 3 node cluster started with ignite.sh and that works perfectly
fine. I'm also able to connect to the cluster with visor and I can also run
top, cache etc... commands no problem.
11 matches
Mail list logo