These are chat archives for atomix/atomix

16th
May 2018
Luca Burgazzoli
@lburgazzoli
May 16 2018 06:52
question, is a listening address really needed for pure ephemeral clients ?
Jordan Halterman
@kuujo
May 16 2018 09:50
It shouldn’t be, but I’m not sure if it’s currently tested.
I’m actually going to refactor the member’s once more tomorrow and I’ll make sure this is the case. The plan is to remove the member types and just treat named members as persistent and unnamed members as ephemeral with a UUID name. This should also mean a client can be started without any local member info whatsoever. Just provide a set of remote members to connect to and start the client.
Back to Atomix tomorrow, and starting the switch to Atomix 2.1 this week as well :-)
We have a bunch of changes in the 2.0 branch to cherry pick
Also need to cherry pick the revision changes still
Luca Burgazzoli
@lburgazzoli
May 16 2018 10:28
great, I'd love to keep the possibility to set my own id for a member but that's not a huge issue
Johno Crawford
@johnou
May 16 2018 12:13
As long as that uuid doesn't change like in ignite.. :)
We need a way of monitoring nodes joining and leaving the cluster
Would need to see what you have in mind
Ronnie
@rroller
May 16 2018 14:54
This should also mean a client can be started without any local member info whatsoever.
That sounds good. Its actually rather painful dealing with local members
in the past using similar libraries (closed sourced ones at Amazon) we'd just bootstrap with a list of nodes and the library would do the rest.
Jordan Halterman
@kuujo
May 16 2018 18:13
@johnou that’s what named nodes are for. If a node has a name then you can keep track of when it connects/disconnects and it’s also safe to use in consensus. Unnamed nodes just get a UUID and can’t be used in consensus since it requires the same node to have the same ID through restarts in order to safely count votes. This is the only real reason for needing to differentiate between the two. If you need information about specific nodes then just name them.
Johno Crawford
@johnou
May 16 2018 18:31
Ok so it would still be possible to have an ephemeral named node?
Jordan Halterman
@kuujo
May 16 2018 18:31
they’ll all be ephemeral, but it wouldn’t really make a difference if they were ephemeral or persistent. The only difference is ephemeral nodes are removed from the configuration, and persistent nodes’ state changes instead
Johno Crawford
@johnou
May 16 2018 18:33
Ah wait old terminology
I mean named node which doesn't participate in consensus
Sounds like a yes from your previous explanation..
Jordan Halterman
@kuujo
May 16 2018 23:01
man the new configuration changes simplify everything… finally think this crap has been figured out