Skip to content
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

Gossip component #2

Closed
timiblossom opened this issue Oct 31, 2013 · 1 comment
Closed

Gossip component #2

timiblossom opened this issue Oct 31, 2013 · 1 comment

Comments

@timiblossom
Copy link
Contributor

This component will help nodes to exchange heartbeats periodically. This paper is what Cassandra based upon for its Gossip implementation: http://www.cs.cornell.edu/home/rvr/papers/flowgossip.pdf. Thanks Brandon Williams from Apache Cassandra for this link.

@timiblossom
Copy link
Contributor Author

It is in

shailesh33 added a commit that referenced this issue Aug 6, 2015
smukil added a commit to smukil/dynomite that referenced this issue Nov 20, 2018
This patch does 3 things:
1) It fixes a longstanding bug in the DynoSpec class that mixed up
   a rack with a DC, causing a cluster of a different topology to
   be created than the one requested.

2) It fixes a small bug introduced in this series of test framework
   commits (in the last 3 commits), which mixed up a client port with
   a internode port.

3) It adds a clear distinction between 'client_port' and 'dnode_port'
   in the DynoSpec class, rather than just having a 'port' field
   which was a source of confusion and led to the above bug (Bug Netflix#2).
smukil added a commit that referenced this issue Sep 29, 2019
This patch does 3 things:
1) It fixes a longstanding bug in the DynoSpec class that mixed up
   a rack with a DC, causing a cluster of a different topology to
   be created than the one requested.

2) It fixes a small bug introduced in this series of test framework
   commits (in the last 3 commits), which mixed up a client port with
   a internode port.

3) It adds a clear distinction between 'client_port' and 'dnode_port'
   in the DynoSpec class, rather than just having a 'port' field
   which was a source of confusion and led to the above bug (Bug #2).
anujphadke pushed a commit to anujphadke/dynomite that referenced this issue Sep 18, 2020
warm up retries update

making start and stop sync consistent

false

return finally

finally Netflix#2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant