-
Notifications
You must be signed in to change notification settings - Fork 78
Another chunk of documentation for beta-1 #952
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| /// A node (or member) is referred to as a "replacement" if it shares _the same_ protocol+host+address (i.e. ``Node``), | ||
| /// with another member; It MAY join "over" an existing node and will immediately cause the previous node to be marked ``Cluster/MemberStatus/down`` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| /// A node (or member) is referred to as a "replacement" if it shares _the same_ protocol+host+address (i.e. ``Node``), | |
| /// with another member; It MAY join "over" an existing node and will immediately cause the previous node to be marked ``Cluster/MemberStatus/down`` | |
| /// A node (or member) is referred to as a "replacement" if it shares _the same_ protocol+host+address (i.e. ``Node``) | |
| /// with another member; it MAY join "over" an existing node and will immediately cause the previous node to be marked ``Cluster/MemberStatus/down`` |
| /// A leader returning a non-nil value, guarantees that the same Member existing as part of this `Membership` as well (non-members cannot be leaders). | ||
| /// A leader is a specific ``Cluster/Member`` which was selected to fulfil the leadership role for the time being. | ||
| /// | ||
| /// A leader returning a non-nil value, guarantees that the same ``Cluster/Member`` existing as part of this ``Cluster/Membership`` as well (non-members cannot be leaders). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| /// A leader returning a non-nil value, guarantees that the same ``Cluster/Member`` existing as part of this ``Cluster/Membership`` as well (non-members cannot be leaders). | |
| /// A leader returning a non-nil value guarantees that the same ``Cluster/Member`` existing as part of this ``Cluster/Membership`` as well (non-members cannot be leaders). |
| ### Leadership | ||
|
|
||
| TODO: document leadership and Leadership changes. | ||
| The cluster is able to use any node discovery mechanism that implements the `ServiceDiscovery` protocol that has an implementation of the `ServiceDiscovery` protocol. like for example: [tuplestream/swift-k8s-service-discovery](https://github.com/tuplestream/swift-k8s-service-discovery) which implements discovery using the kubernetes (k8s) APIs: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The cluster is able to use any node discovery mechanism that implements the `ServiceDiscovery` protocol that has an implementation of the `ServiceDiscovery` protocol. like for example: [tuplestream/swift-k8s-service-discovery](https://github.com/tuplestream/swift-k8s-service-discovery) which implements discovery using the kubernetes (k8s) APIs: | |
| The cluster is able to use any node discovery mechanism that implements the `ServiceDiscovery` protocol. For example: [tuplestream/swift-k8s-service-discovery](https://github.com/tuplestream/swift-k8s-service-discovery) which implements discovery using the kubernetes (k8s) APIs: |
| > order to let others know they are available to meet now. | ||
| Checking-in with the receptionist is performed by calling ``DistributedReceptionist/checkIn(_:with:)`` and passing a | ||
| specific key; The key is useful for when the same types of actor, may want to perform different roles. For example, you may |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| specific key; The key is useful for when the same types of actor, may want to perform different roles. For example, you may | |
| specific key. The key is useful for when the same type of actors may want to perform different roles. For example, you may |
Resolves #927 for the first beta release.
We'll be adding much more docs, but this is a good enough first cut.