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] Update of "WritePathForUsers" by MichaelEdge
Date Tue, 01 Dec 2015 02:28:05 GMT
Dear Wiki user,

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

The "WritePathForUsers" page has been changed by MichaelEdge:
https://wiki.apache.org/cassandra/WritePathForUsers?action=diff&rev1=28&rev2=29

  When a local coordinator is unable to send data to a replica node due to the replica node
being unavailable, the local coordinator stores the data either in its local system.hints
table (prior to Cassandra v3.0) or in a local flat file (from Cassandra v3.0 onwards); this
process is known as Hinted Handoff and is configured in cassandra.yaml. Hint data is stored
for a default period of 3 hours, configurable using the max_hint_window_in_ms property in
cassandra.yaml. If the replica node comes back online within the hinted handoff window the
local coordinator will send the data to the replica node, otherwise the hint data is discarded
and the replica node will need to be repaired.
  == Write Path Advantages ==
   * The write path is one of Cassandra’s key strengths: for each write request one sequential
disk write plus one in-memory write occur, both of which are extremely fast.
- 
- ---- /!\ '''Edit conflict - other version:''' ----
   * During a write operation, Cassandra never reads before writing (with the exception of
Counters), never rewrites data, never deletes data and never performs random I/O.
  
- ---- /!\ '''Edit conflict - your version:''' ----
-  * During a write operation, Cassandra never reads before writing (with the exception of
Counters), never rewrites data, never deletes data and never performs random I/O.
- 
- ---- /!\ '''End of edit conflict''' ----
- 

Mime
View raw message