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 2013/02/01 23:30:05 UTC

[Cassandra Wiki] Update of "HadoopSupport" by jeremyhanna

Dear Wiki user,

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

The "HadoopSupport" page has been changed by jeremyhanna:
http://wiki.apache.org/cassandra/HadoopSupport?action=diff&rev1=55&rev2=56

  If you are running into timeout exceptions, you might need to tweak one or both of these settings:
  
   * '''cassandra.range.batch.size''' - the default is 4096, but you may need to lower this depending on your data.  This is either specified in your hadoop configuration or using `org.apache.cassandra.hadoop.ConfigHelper.setRangeBatchSize`.
-  * '''rpc_timeout_in_ms''' - this is set in your `cassandra.yaml` (in 0.6 it's `RpcTimeoutInMillis` in `storage-conf.xml`).  The rpc timeout is not for timing out from the client but between nodes.  This can be increased to reduce chances of timing out.
+  * '''rpc_timeout_in_ms''' - this is set in your `cassandra.yaml`.  The rpc timeout is not for timing out from the client but between nodes.  This can be increased to reduce chances of timing out.
  
  If you still see timeout exceptions with resultant failed jobs and/or blacklisted tasktrackers, there are settings that can give Cassandra more latitude before failing the jobs.  An example of usage (in either the job configuration or tasktracker mapred-site.xml):