Hello! Since you can use Java system properties in XMLs and you can specify those on cmdline, should be not hard to automate DevOps here.
Glad that you have it working. Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 10:57, wiltu <[email protected]>: > Hello! > Yep, "172.20.0.1" is a docker network IP, like this : > ============================================= > 6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue > state > DOWN group default > link/ether 02:42:56:dd:06:b5 brd ff:ff:ff:ff:ff:ff > inet 172.17.0.1/16 scope global docker0 > valid_lft forever preferred_lft forever > 11: docker_gwbridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc > noqueue state UP group default > link/ether 02:42:7f:c3:f0:89 brd ff:ff:ff:ff:ff:ff > inet 172.18.0.1/16 brd 172.18.255.255 scope global docker_gwbridge > valid_lft forever preferred_lft forever > inet6 fe80::42:7fff:fec3:f089/64 scope link > valid_lft forever preferred_lft forever > ============================================= > > My docker use host network driver for container, and this cluster can work > for a while (maybe up 12 hours ) , the means TcpCommunicationSpi is working > at the beginning. Maybe specify localAddress can make the cluster to work, > but does not seem to fit the principle of auto DevOps. > Then I tried to change the cluster to another machine, it live 2 days and > looks good. > I want it to run for a few days under observation. > > Thank you very much, I have benefited a lot from your suggestion, Please > let > me know if you have any suggestions. > > Regards, > Wilson > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
