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 <[email protected]>: > 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 <[email protected] wrote: > >> 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 at 14:12, John Smith <[email protected]> wrote: >> >>> 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 <[email protected]> wrote: >>> >>>> I can confirm I just tested it. There is no stack trace. Basically the >>>> client connects, no errors, the cache command hangs/pauses, I disconnect >>>> the client and cache command completes. I'm also 100% certain the client >>>> works when connecting to the cluster over wi-fi. I have been able to create >>>> caches dynamically. Query the caches etc... >>>> >>>> On Fri, 11 Jan 2019 at 12:23, John Smith <[email protected]> >>>> wrote: >>>> >>>>> 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 < >>>>> [email protected]> wrote: >>>>> >>>>>> 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 < >>>>>> [email protected]>: >>>>>> >>>>>>> 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 <[email protected]>: >>>>>>> >>>>>>>> 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 < >>>>>>>> [email protected]> 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 <[email protected]>: >>>>>>>>> >>>>>>>>>> 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. But the issue >>>>>>>>>> arises >>>>>>>>>> only when an external client node connects >>>>>>>>>> using igniteConfig.setClientMode(true); >>>>>>>>>> >>>>>>>>>> 1- Start the cluster >>>>>>>>>> 2- Connect with visor >>>>>>>>>> 3- Run cache command (prints cache details, no problem) >>>>>>>>>> 4- Connect client application >>>>>>>>>> 5- Run cache command (seems to hang, doesn't crash) >>>>>>>>>> 6- Disconnect client app >>>>>>>>>> 7- Cache command completes and prints. >>>>>>>>>> >>>>>>>>>> Cache seems to be the only command that hangs/pauses when the >>>>>>>>>> client is connected. >>>>>>>>>> >>>>>>>>>> The cache config incase... >>>>>>>>>> >>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>>>>>>> >>>>>>>>>> <beans xmlns="http://www.springframework.org/schema/beans"; >>>>>>>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>>>>>>>>> xmlns:util="http://www.springframework.org/schema/util"; >>>>>>>>>> xsi:schemaLocation=" >>>>>>>>>> http://www.springframework.org/schema/beans >>>>>>>>>> >>>>>>>>>> http://www.springframework.org/schema/beans/spring-beans.xsd >>>>>>>>>> >>>>>>>>>> http://www.springframework.org/schema/util >>>>>>>>>> >>>>>>>>>> http://www.springframework.org/schema/util/spring-util.xsd";> >>>>>>>>>> <bean >>>>>>>>>> class="org.apache.ignite.configuration.IgniteConfiguration"> >>>>>>>>>> <property name="igniteInstanceName" value="xxxxxx-dev"/> >>>>>>>>>> >>>>>>>>>> <property name="discoverySpi"> >>>>>>>>>> <bean >>>>>>>>>> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> >>>>>>>>>> <property name="ipFinder"> >>>>>>>>>> <bean >>>>>>>>>> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> >>>>>>>>>> <property name="addresses"> >>>>>>>>>> <list> >>>>>>>>>> >>>>>>>>>> <value>xxxxxx-1:47500..47510</value> >>>>>>>>>> >>>>>>>>>> <value>xxxxxx-2:47500..47510</value> >>>>>>>>>> >>>>>>>>>> <value>xxxxxx-3:47500..47510</value> >>>>>>>>>> </list> >>>>>>>>>> </property> >>>>>>>>>> </bean> >>>>>>>>>> </property> >>>>>>>>>> </bean> >>>>>>>>>> </property> >>>>>>>>>> >>>>>>>>>> <property name="dataStorageConfiguration"> >>>>>>>>>> <bean >>>>>>>>>> class="org.apache.ignite.configuration.DataStorageConfiguration"> >>>>>>>>>> <property name="defaultDataRegionConfiguration"> >>>>>>>>>> <bean >>>>>>>>>> class="org.apache.ignite.configuration.DataRegionConfiguration"> >>>>>>>>>> <property name="maxSize" >>>>>>>>>> value="8589934592"/> >>>>>>>>>> <property name="persistenceEnabled" >>>>>>>>>> value="true"/> >>>>>>>>>> </bean> >>>>>>>>>> </property> >>>>>>>>>> </bean> >>>>>>>>>> </property> >>>>>>>>>> >>>>>>>>>> <property name="cacheConfiguration"> >>>>>>>>>> <list> >>>>>>>>>> <bean >>>>>>>>>> class="org.apache.ignite.configuration.CacheConfiguration"> >>>>>>>>>> <property name="name" value="Replicated"/> >>>>>>>>>> <property name="cacheMode" >>>>>>>>>> value="REPLICATED"/> >>>>>>>>>> <property name="atomicityMode" >>>>>>>>>> value="ATOMIC"/> >>>>>>>>>> <property name="copyOnRead" value="true"/> >>>>>>>>>> </bean> >>>>>>>>>> >>>>>>>>>> <bean >>>>>>>>>> class="org.apache.ignite.configuration.CacheConfiguration"> >>>>>>>>>> <property name="name" value="Partitioned"/> >>>>>>>>>> <property name="cacheMode" >>>>>>>>>> value="PARTITIONED"/> >>>>>>>>>> <property name="atomicityMode" >>>>>>>>>> value="ATOMIC"/> >>>>>>>>>> <property name="backups" value="1"/> >>>>>>>>>> <property name="readFromBackup" value="true"/> >>>>>>>>>> <property name="copyOnRead" value="true"/> >>>>>>>>>> </bean> >>>>>>>>>> </list> >>>>>>>>>> </property> >>>>>>>>>> </bean> >>>>>>>>>> </beans> >>>>>>>>>> >>>>>>>>>
