cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cassandra Wiki] Trivial Update of "ArchitectureGossip" by shirishreddy
Date Sat, 13 Mar 2010 12:31:58 GMT
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 shirishreddy.
The comment on this change is: Spell correction.
http://wiki.apache.org/cassandra/ArchitectureGossip?action=diff&rev1=3&rev2=4

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

  
  == 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 disginguishing 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 bootsrapping would
have "bootstrapping" application state: (bxLpassF3XD8Kyks, 56) where first one is bootsrap
token, and the second is version. Version number is shared by application states and HeartBeatState
to guarantee ordering and can only grow.
+ 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.
  
  ==== EndPointState ====
  Includes all ApplicationStates and HeartBeatState for certain endpoint (node). EndPointState
can include only one of each type of ApplicationState, so if EndPointState already includes,
say, load information, new load information will overwrite the old one. ApplicationState version
number guarantees that old value will not overwrite new one.

Mime
View raw message