You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by Apache Wiki <wi...@apache.org> on 2011/04/22 17:15:40 UTC

[Cassandra Wiki] Update of "ArchitectureGossip" by MakiWatanabe

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.

The "ArchitectureGossip" page has been changed by MakiWatanabe.
The comment on this change is: Add description of HeartBeatState Generation.
http://wiki.apache.org/cassandra/ArchitectureGossip?action=diff&rev1=7&rev2=8

--------------------------------------------------

  
  == Data structures ==
  ==== HeartBeatState ====
- Consists of generation and version number. Generation stays the same when server is running and grows every time the node is started. Used for distinguishing state information before and after a node restart. Version number is shared with application states and guarantees ordering. Each node has one !HeartBeatState associated with it.
+ Consists of generation and version number. Generation is the timestamp when the node is started, represented by seconds since 1970/01/01. It stays the same when server is running and grows every time the node is started. Used for distinguishing state information before and after a node restart. Version number is shared with application states and guarantees ordering. Each node has one !HeartBeatState associated with it.
  
  ==== ApplicationState ====
  Consists of state and version number and represents a state of single "component" or "element" within Cassandra. For instance application state for "load information" could be (5.2, 45), which means that node load is 5.2 at version 45. Similarly a node that is bootstrapping would have "bootstrapping" application state: (bxLpassF3XD8Kyks, 56) where first one is bootstrap token, and the second is version. Version number is shared by application states and !HeartBeatState to guarantee ordering and can only grow.