--
You received this message because you are subscribed to a topic in the Google Groups "vert.x" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vertx/3JTLkaGwXh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/c4b84b35-2a40-4bd7-8b69-c99039002508%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
2016-09-17 15:31:28.191 | WARN | .0.1:2181) | rg.apache.zookeeper.ClientCnxn:1102) | Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnectjava.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:1.8.0_92] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) ~[?:1.8.0_92] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361) ~[vertx-docker-test-fat.jar:?] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081) [vertx-docker-test-fat.jar:?]2016-09-17 15:31:29.301 | INFO | .0.1:2181) | rg.apache.zookeeper.ClientCnxn::975) | Opening socket connection to server 127.0.0.1/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)2016-09-17 15:31:29.302 | WARN | .0.1:2181) | rg.apache.zookeeper.ClientCnxn:1102) | Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnectjava.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:1.8.0_92] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) ~[?:1.8.0_92] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361) ~[vertx-docker-test-fat.jar:?] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081) [vertx-docker-test-fat.jar:?]2016-09-17 15:31:30.077 | RROR | r-thread-0 | apache.curator.ConnectionState::200) | Connection timed out for connection string (127.0.0.1) and timeout (3000) / elapsed (16339)org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = ConnectionLoss at org.apache.curator.ConnectionState.checkTimeouts(ConnectionState.java:197) ~[vertx-docker-test-fat.jar:?] at org.apache.curator.ConnectionState.getZooKeeper(ConnectionState.java:88) ~[vertx-docker-test-fat.jar:?]
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/9734e48c-e451-4005-ad49-6809edc87b3d%40googlegroups.com.
On Sep 17, 2016, at 3:04 PM, Christian Vogel <christi...@kimengi.com> wrote:
To your second question, Vert.x also supports Zookeeper as a cluster manager, you could try using that.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/1e0dbca1-562f-4411-9c5d-6f69dd868236%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/c403074d-c66a-4bc1-8eef-5fcbcc5ebf76%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/ccce3a2d-5307-434c-ae93-10a8ed9f5c43%40googlegroups.com.
Sep 19, 2016 12:13:09 PM com.hazelcast.nio.tcp.TcpIpConnectionINFO: [172.17.0.2]:5701 [dev] [3.6.3] Connection [Address[172.17.0.5]:5701] lost. Reason: java.io.EOFException[Remote socket closed!]Sep 19, 2016 12:13:09 PM com.hazelcast.nio.tcp.nonblocking.NonBlockingSocketReaderWARNING: [172.17.0.2]:5701 [dev] [3.6.3] hz._hzInstance_1_dev.IO.thread-in-0 Closing socket to endpoint Address[172.17.0.5]:5701, Cause:java.io.EOFException: Remote socket closed!Sep 19, 2016 12:13:11 PM com.hazelcast.nio.tcp.InitConnectionTaskINFO: [172.17.0.2]:5701 [dev] [3.6.3] Connecting to /172.17.0.5:5701, timeout: 0, bind-any: trueSep 19, 2016 12:13:56 PM com.hazelcast.cluster.impl.ClusterHeartbeatManagerWARNING: [172.17.0.2]:5701 [dev] [3.6.3] This node does not have a connection to Member [172.17.0.5]:5701
Can you verify that the container is shut down gracefully? The cluster manager should call HazelcastInstance#shutdown when the node is leaving, which should send the signal to other members (unless an exsiting HazelcastInstance was provided externally).
2016-09-17 20:00 GMT+02:00 lukjel <l.zeli...@gmail.com>:
You can use my simple project as a reproducer: https://github.com/lukjel/vertx-cluster-docker-test (I know it's not as simple as it should be...)You can test on "clean" environment. I described how to setup new machine (google cloud) with docker and deploy cluster with 4 "nodes".Reg.-l.
W dniu sobota, 17 września 2016 19:24:25 UTC+2 użytkownik Jochen Mader napisał:I think it would be great to have a reproducer for that performance degredation you are seeing with ignite.The luster-manager shouldn't have such a big impact on message-transfer as it only syncs a map of cluster-members and registered addresses between the nodes.The actual sending is done directly between nodes.Sounds like a contention problem in the Ignite-module.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/6b08d556-4b6a-4088-82a0-5e1cd905f606%40googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/6b08d556-4b6a-4088-82a0-5e1cd905f606%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/48f1e31a-570a-4c3a-8987-a4bb11be2394%40googlegroups.com.
Thanks Thomas.1. I created Dockerfile in the way how it is described in official documentation. IMHO there should be some update about vert.x and docker and fat-jar.
2. There is still a problem with killing one node in not so graceful way. Any idea?
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/9bcdcb86-6992-448a-bd78-f5c264c65ff9%40googlegroups.com.
2016-09-20 17:36 GMT+02:00 lukjel <l.zeli...@gmail.com>:Thanks Thomas.1. I created Dockerfile in the way how it is described in official documentation. IMHO there should be some update about vert.x and docker and fat-jar.Or vertx-examples repo? Or both I guess?
2. There is still a problem with killing one node in not so graceful way. Any idea?With my local testing I couldn't reproduce issues like yours. Well the node couldn't signal its leaving so it took some time for other nodes to detect the failure, but this is pretty normal and the cluster was rebalanced after a few seconds.
-Dhazelcast.max.no.heartbeat.seconds=5
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/c0641ec0-8266-4ddd-9eb4-40d8f5c4a3f8%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/c0641ec0-8266-4ddd-9eb4-40d8f5c4a3f8%40googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/c0a7a0e5-0fb8-4bd8-8c6b-dd3bb4510e12%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/c0a7a0e5-0fb8-4bd8-8c6b-dd3bb4510e12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/DE13B111-790D-4749-8C2E-866E11EB3794%40gmail.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/c0a7a0e5-0fb8-4bd8-8c6b-dd3bb4510e12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/DE13B111-790D-4749-8C2E-866E11EB3794%40gmail.com.
So...I can confirm - after Dockerfile change - docker stop works properly and cluster rebalanced. However when I run "docker kill" then it takes much more than one minute to rebalance. It's not good.
And finnaly I found a solution! There is hazelcast parameter hazelcast.max.no.heartbeat.secondsAnd it is exactly what it sounds to be. Default value is 300 so it takes about 5 minutes to rebalance.When I set this parameter to 5 then it works as I expect.To set this parameter you have to add this to your java command:
-Dhazelcast.max.no.heartbeat.seconds=5
Officialy - problem solved. (documentation and examples of docker and fat-jar has to be corrected - how to report this? should I add an issue?)
Thanks to all involved!
LukasPS.Here are some other VERY interesting parameters for hazelcast:
W dniu wtorek, 20 września 2016 18:27:41 UTC+2 użytkownik lukjel napisał:Hi
W dniu wtorek, 20 września 2016 17:55:47 UTC+2 użytkownik Thomas Segismont napisał:2016-09-20 17:36 GMT+02:00 lukjel <l.zeli...@gmail.com>:Thanks Thomas.1. I created Dockerfile in the way how it is described in official documentation. IMHO there should be some update about vert.x and docker and fat-jar.Or vertx-examples repo? Or both I guess?Both :D2. There is still a problem with killing one node in not so graceful way. Any idea?With my local testing I couldn't reproduce issues like yours. Well the node couldn't signal its leaving so it took some time for other nodes to detect the failure, but this is pretty normal and the cluster was rebalanced after a few seconds.Here's the rub!My cluster rebalanced after very long period. I didn't measure it but it's more like 1 minute. This is much too long.I tested the scenario with Apache Ignite and there wasn't such problem.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/c0641ec0-8266-4ddd-9eb4-40d8f5c4a3f8%40googlegroups.com.