Dmitry, Recently, I've faced the same issue. I've tried configs from `example` Ignite directory and they worked for me. Try: ./ignite.sh -v example/config/example-ignite.xml
Note. You should have the correct IGNITE_HOME environment variable pointing at yours Ignite dir. Is this is what you need? On Fri, 7 Sep 2018 at 19:19 Dmitry Melnichuk <dmitry.melnic...@nobitlost.com> wrote: > Alexey, > > Yes, I believe I am using the default config. I do not modify any file > of those came with Ignite nightly build, and I do not supply my own .xml > to `bin/ignite.sh` script, so I think I'm clean. > > Could you please clarify, which exactly file to edit and how to set > `TcpDiscoveryVmIpFinder` up with proper value? I am not a Java developer > and not familiar with Ignite fine tuning. > > On 9/7/18 6:54 PM, Alexey Goncharuk wrote: > > Hello Dmitriy, > > > > Did you use the default config shipped with Ignite? Can you try modifying > > the config to use TcpDiscoveryVmIpFinder providing only 127.0.0.1:47500 > in > > the list of IP addresses? > > > > чт, 6 сент. 2018 г. в 22:16, Dmitry Melnichuk < > > dmitry.melnic...@nobitlost.com>: > > > >> Hello igniters! > >> > >> I am again in need of your mighty helping hand. > >> > >> Recently I experienced a strange bug. It may be a fresh regression, or > >> maybe I myself did something wrong. It would be great if someone looked > >> into this matter. > >> > >> I have a need of testing some things in my client against a cluster of > >> multiple Ignite instances. If my understanding is correct, I can create > >> an Ignite cluster on localhost just by launching multiple > >> `bin/ignite.sh` in console(s) with no special parameters. I tried doing > >> so, but each Ignite instance I created was forming a separate cluster, > >> and no data sharing occurred. > >> > >> I was told that in some cases IPv6 may prevent default Ignite instances > >> from gathering into a cluster, at least there was a same or similar case > >> with Ignite 2.7 on fresh MacOS X. I disabled IPv6 with > >> > >> ``` > >> $ _JAVA_OPTIONS=-Djava.net.preferIPv4Stack=true bin/ignite.sh > >> ``` > >> > >> but the outcome did not change. For me it looks like clustering is > >> enabled, but instances can not detect each other's presence. > >> > >> My OS is Arch Linux. This is my java version: > >> > >> ``` > >> $ java -version > >> openjdk version "1.8.0_181" > >> OpenJDK Runtime Environment (build 1.8.0_181-b13) > >> OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode) > >> ``` > >> > >> Output of the first console: > >> > >> ``` > >> >>> +------------------------------------------+ > >> >>> Ignite ver. 2.7.0.20180830#19700101-sha1:DEV > >> >>> +------------------------------------------+ > >> >>> OS name: Linux 4.18.3-arch1-1-ARCH amd64 > >> >>> CPU(s): 4 > >> >>> Heap: 1.0GB > >> >>> VM name: 20751@ibmpc > >> >>> Local node [ID=FD43A01E-C0D1-4ED3-A653-036982C0205F, order=1, > >> clientMode=false] > >> >>> Local node addresses: [ibmpc/127.0.0.1, ibmpc/192.168.0.222, > >> /192.168.122.1] > >> >>> Local ports: TCP:8080 TCP:10800 TCP:11211 TCP:47100 UDP:47400 > >> TCP:47500 > >> > >> [07-09-2018 03:39:41][INFO ][main][GridDiscoveryManager] Topology > >> snapshot [ver=1, servers=1, clients=0, CPUs=4, offheap=3.1GB, > heap=1.0GB] > >> [07-09-2018 03:39:41][INFO ][main][GridDiscoveryManager] ^-- Node > >> [id=FD43A01E-C0D1-4ED3-A653-036982C0205F, clusterState=ACTIVE] > >> [07-09-2018 03:39:41][INFO ][main][GridDiscoveryManager] Data Regions > >> Configured: > >> [07-09-2018 03:39:41][INFO ][main][GridDiscoveryManager] ^-- default > >> [initSize=256.0 MiB, maxSize=3.1 GiB, persistenceEnabled=false] > >> > >> ``` > >> > >> Second console: > >> ``` > >> >>> +------------------------------------------+ > >> >>> Ignite ver. 2.7.0.20180830#19700101-sha1:DEV > >> >>> +------------------------------------------+ > >> >>> OS name: Linux 4.18.3-arch1-1-ARCH amd64 > >> >>> CPU(s): 4 > >> >>> Heap: 1.0GB > >> >>> VM name: 20168@ibmpc > >> >>> Local node [ID=108D943D-CE66-4A5D-B8DD-F59F199F4E66, order=1, > >> clientMode=false] > >> >>> Local node addresses: [ibmpc/127.0.0.1, ibmpc/192.168.0.222, > >> /192.168.122.1] > >> >>> Local ports: TCP:8081 TCP:10801 TCP:11212 TCP:47101 UDP:47400 > >> TCP:47501 > >> > >> [07-09-2018 03:37:13][INFO ][main][GridDiscoveryManager] Topology > >> snapshot [ver=1, servers=1, clients=0, CPUs=4, offheap=3.1GB, > heap=1.0GB] > >> [07-09-2018 03:37:13][INFO ][main][GridDiscoveryManager] ^-- Node > >> [id=108D943D-CE66-4A5D-B8DD-F59F199F4E66, clusterState=ACTIVE] > >> ``` > >> > >> Third console: > >> `>>> +------------------------------------------+ > >> >>> Ignite ver. 2.7.0.20180830#19700101-sha1:DEV > >> >>> +------------------------------------------+ > >> >>> OS name: Linux 4.18.3-arch1-1-ARCH amd64 > >> >>> CPU(s): 4 > >> >>> Heap: 1.0GB > >> >>> VM name: 20433@ibmpc > >> >>> Local node [ID=40D54138-491D-4AF9-BD10-5A3B53E38E77, order=1, > >> clientMode=false] > >> >>> Local node addresses: [ibmpc/127.0.0.1, ibmpc/192.168.0.222, > >> /192.168.122.1] > >> >>> Local ports: TCP:8082 TCP:10802 TCP:11213 TCP:47102 UDP:47400 > >> TCP:47502 > >> > >> [07-09-2018 03:38:23][INFO ][main][GridDiscoveryManager] Topology > >> snapshot [ver=1, servers=1, clients=0, CPUs=4, offheap=3.1GB, > heap=1.0GB] > >> [07-09-2018 03:38:23][INFO ][main][GridDiscoveryManager] ^-- Node > >> [id=40D54138-491D-4AF9-BD10-5A3B53E38E77, clusterState=ACTIVE] > >> [07-09-2018 03:38:23][INFO ][main][GridDiscoveryManager] Data Regions > >> Configured: > >> [07-09-2018 03:38:23][INFO ][main][GridDiscoveryManager] ^-- default > >> [initSize=256.0 MiB, maxSize=3.1 GiB, persistenceEnabled=false]`` > >> > >> ``` > >> > >> Dmitry > >> > > > > -- -- Maxim Muzafarov
