partisan
partisan copied to clipboard
lasp-lang
High-performance, high-scalability distributed computing for the BEAM.
All of the `neighbor`, `neighbor_accepted` and `neighbor_rejected` messages in the HyParView implementation need acknowledgements, and the messages buffered until so, to ensure the views are symmetric.
It's unclear how to explicitly leave from the cluster outside of a failure, given the algorithm in the paper doesn't directly discuss this.
In HyParView, when the shuffle occurs and members of the remote passive view are replaced the nodes that are randomly evicted out of the passive side of the recipient should...
All of the `handle_message` calls coming off of the socket should be made asynchronous.
The default membership for partisan does not persist the actor for a given instance of the peer service manager: this is something we inherited from Helium's peer service. Because of...
`` doesn't seem to be supported by `ex_doc`:  Using a end-of-line double space convention instead fixes this: 
This happens when a message is fast forwarded. The sending function checks we have a connection for Channel/Node, prepares the message and the sends. Concurrently the peer service might decide...
Hi @aramallo, I noticed also the even after re-booting all the components in the cluster, the AAE is still consideringnodes that are not supposed to be in the cluster. In...
Likely related to #251, when nodes go down and up a few times (usually when debugging apps!), dynamic node names appear apparently randomly, and for some reason this leads to...