These are chat archives for atomix/atomix

13th
Mar 2018
Colas
@LitlBro
Mar 13 2018 15:46
@mac01021 my use case is somehow similar. My node are spawn on random machines so I have no clues about their host or available port.
The solution for now is a known, external application. future nodes connects to a server, give their host/port. after a while, the application notice the nodes of the collection of host/port. Starting from there I can build my cluster and remove the external temporary server. Did not find any other way though
Colas
@LitlBro
Mar 13 2018 16:12
(the Atomix cluster is on top of hadoop/yarn, which dynamically allow containers to run the nodes, and the external application is a akka-http server on the application master)
Jordan Halterman
@kuujo
Mar 13 2018 21:41
Sorry I was traveling all last week and I’m traveling again this week but then I’m staying home for a while :-)
But my travels bring Atomix bug fixes :-P
Tej
@vvstej
Mar 13 2018 23:00
what would be the cause of io.atomix.copycat.session.ClosedSessionException: session closed
at io.atomix.copycat.client.session.ClientSession.submit(ClientSession.java:132)
at io.atomix.copycat.client.DefaultCopycatClient.submit(DefaultCopycatClient.java:233)
at io.atomix.AtomixReplica$CombinedCopycatClient.submit(AtomixReplica.java:996)
at io.atomix.manager.resource.internal.InstanceClient.submit(InstanceClient.java:145)
at io.atomix.resource.internal.ResourceCopycatClient.submit(ResourceCopycatClient.java:83)
at io.atomix.collections.DistributedMap.keySet(DistributedMap.java:1072)
at com.salesforce.automation.precheckin.server.container.AtomixContainer.getIds(AtomixContainer.java:140)
what could be the cause of closed session exceptions, I see these randomly occurring during the course of my distributed cluster running
and whats the resolution for it? for now I am restarting the server , but would be problematic in production if this happens frequently
and sometimes the nodes infinitely keep trying to connect to each other. Even though there isnt any network partitioning
2018-03-13 23:04:21,714 INFO copycat-client-io-1 NettyClient:66 - Connecting to mirror-pcs-1-prd404.eng.sfdc.net/10.252.200.46:12002
2018-03-13 23:04:21,715 INFO catalyst-event-loop-2 NettyClient:98 - Connected to mirror-pcs-1-prd404.eng.sfdc.net/10.252.200.46:12002
Tej
@vvstej
Mar 13 2018 23:05
and then again
2018-03-13 23:04:22,465 INFO copycat-client-io-1 NettyClient:66 - Connecting to mirror-pcs-1-prd410.eng.sfdc.net/10.252.206.126:12002
2018-03-13 23:04:22,466 INFO catalyst-event-loop-3 NettyClient:98 - Connected to mirror-pcs-1-prd410.eng.sfdc.net/10.252.206.126:12002
this just happens infinitely