Maxim,
Thank you very much, your command did it. I did not had to set the
`IGNITE_HOME` var though.
Now I must analyze the difference it made to put in into my client's
documentation.
On 9/8/18 2:27 AM, Maxim Muzafarov wrote:
Dmitry,
Recently, I've faced the same issue. I've tried configs
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?
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
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 a
