cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject ArchitectureGossip reverted to revision 7 on Cassandra Wiki
Date Sat, 23 Apr 2011 07:56:01 GMT
Dear wiki user,

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

The page ArchitectureGossip has been reverted to revision 7 by MakiWatanabe.
The comment on this change is: Need to study more on Generation number logic.
http://wiki.apache.org/cassandra/ArchitectureGossip?action=diff&rev1=8&rev2=9

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

  
  == Data structures ==
  ==== HeartBeatState ====
- 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.
+ 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.
  
  ==== 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.

Mime
View raw message