These are chat archives for atomix/atomix
@himanshug sorry your last question got lost to the cavern that is the top of my monitor. What you said is right. For safety, configurations are stored on disk. That complicates managing clusters that evolve a lot. The weird thing is, a node can crash and the cluster can evolve while it's down, but as long as at least one still existing and live node is in its configuration it will eventually find the new nodes and get the new configuration.
@jhalterman and I were actually just talking about how to replace a node's configuration but keep the logs. Currently, that's not possible but I think it can be made possible with relatively little work.
Anyways, you can remove a member of the cluster with
server.cluster().member(someAddress).remove(). TBH this isn't well tested. We haven't really done any work that uses that method, and looking at it I can't say it works. It should be fairly trivial to implement, in just not so sure that code is doing what it says it does right now :-P
DistributedValue. Define a
Resourceinterface, define a
ResourceStateMachine, define a set of commands, and implement methods on the state machine.