These are chat archives for atomix/atomix

1st
Jan 2016
Richard Pijnenburg
@electrical
Jan 01 2016 10:43
@kuujo @jhalterman happy new year guys :)
Jordan Halterman
@kuujo
Jan 01 2016 10:43
you too!
spending my 2016 thus far improving documentation for release :-) whenever that is
probably will be hitting some EC2 instances today though
Richard Pijnenburg
@electrical
Jan 01 2016 10:49
Haha. Isn't it like 3 am or something for you ?
Jordan Halterman
@kuujo
Jan 01 2016 10:51
yeah I was sick yesterday so was sleeping until really late and now my night is all messed up :-P
Richard Pijnenburg
@electrical
Jan 01 2016 10:52
Haha. Know that feeling yeah.
I'm recovering from the drinking from yesterday.
Jordan Halterman
@kuujo
Jan 01 2016 10:56
haha
new years will do that to you
Richard Pijnenburg
@electrical
Jan 01 2016 10:57
Haha yeah. Or any decent party lol
Richard Pijnenburg
@electrical
Jan 01 2016 11:05
I built the new jar yesterday. Will do some testing later today
As soon as my head feels normal. Lol
Jordan Halterman
@kuujo
Jan 01 2016 11:06
lol awesome
I fixed a couple more little things, and so the Atomix tests seem to be passing again
Richard Pijnenburg
@electrical
Jan 01 2016 11:07
Ah nice. Will rebuild it then and try it out.
Jordan Halterman
@kuujo
Jan 01 2016 11:07
Travis is still seeing a couple Copycat tests fail, but I’m getting consistent success on my local. I’ll set up a VM and try to reproduce that some time, but it’s definitely looking a lot better
definitely gonna do some stuff on EC2 ASAP
Richard Pijnenburg
@electrical
Jan 01 2016 11:08
I did had a test failure the first time yeah. Second try it all passed
Didn't write down which test messed up
Jordan Halterman
@kuujo
Jan 01 2016 11:16
The crappy thing is Travis doesn’t make it easy to see what’s wrong in tests. I can’t enable debug logging because the logs are so verbose that Travis fails the tests for having too much output, so there’s not much I can glean from the failed tests. But a VM might help
Richard Pijnenburg
@electrical
Jan 01 2016 11:18
Hehe yeah indeed. That's why I moved away from Travis and use jenkins these days
Running fully with docker slaves :)
Jordan Halterman
@kuujo
Jan 01 2016 11:29
nice
Jordan Halterman
@kuujo
Jan 01 2016 13:51
Actually found another little bug that could be related to those test failures, but now I'm too tired to play with it any more. Back to sleep!
Richard Pijnenburg
@electrical
Jan 01 2016 13:52
Haha. Catch you later bud.
Richard Pijnenburg
@electrical
Jan 01 2016 13:57
Btw. Just did my simple test with 3 nodes and a client. Fails horribly after a minute or so.
Jordan Halterman
@kuujo
Jan 01 2016 13:59
What does the test do and what does a failure mean?
Richard Pijnenburg
@electrical
Jan 01 2016 14:01
I start 3 nodes that form the raft cluster. Then I start a very simple client that does nothing except connect to it and loses connection and fails to re connect.
Cluster it self falls over as well with connection issues. And unknown session errors
Seeing a lot of client connection errors saying failed to connect to the cluster
Jordan Halterman
@kuujo
Jan 01 2016 14:03
That unknown session error is what I found a while ago
Sounds like something else though
Richard Pijnenburg
@electrical
Jan 01 2016 14:05
i can gist the logs if that helps.
Jordan Halterman
@kuujo
Jan 01 2016 14:05
"Failed to connect" doesn't necessarily mean it couldn't connect to a server, it means it couldn't commit to the cluster.
Sure I'll run it on EC2 in the afternoon and see what I see
Richard Pijnenburg
@electrical
Jan 01 2016 14:05
okay. I'll gist the logs and link it here.
its a lot of logs :-)
Richard Pijnenburg
@electrical
Jan 01 2016 19:45
@kuujo i noticed in the client log that it never logs that it lost connection or anything.
only that its making a connection