<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>DataStax Support Forums &#187; Tag: replication factor - Recent Posts</title>
		<link>http://www.datastax.com/support-forums/tags/replication-factor</link>
		<description>Software, Support, and Training for Apache Cassandra</description>
		<language>en-US</language>
		<pubDate>Thu, 20 Jun 2013 11:53:18 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.3</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://www.datastax.com/support-forums/search.php</link>
		</textInput>
		<atom:link href="http://www.datastax.com/support-forums/rss/tags/replication-factor" rel="self" type="application/rss+xml" />

		<item>
			<title>rob4you on "Nodes were Unavailable"</title>
			<link>http://www.datastax.com/support-forums/topic/nodes-were-unavailable/page/2#post-7242</link>
			<pubDate>Wed, 31 Oct 2012 00:09:58 +0000</pubDate>
			<dc:creator>rob4you</dc:creator>
			<guid isPermaLink="false">7242@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;The problem doesn't seem to have been fixed.&#60;/p&#62;
&#60;p&#62;Look at this snippet:&#60;/p&#62;
&#60;p&#62;&#38;gt; CREATE KEYSPACE a WITH strategy_class = 'org.apache.cassandra.locator.SimpleStrategy' AND strategy_options:replication_factor='1';&#60;/p&#62;
&#60;p&#62;&#38;gt; DESCRIBE KEYSPACE a;&#60;br /&#62;
CREATE KEYSPACE a WITH strategy_class = 'SimpleStrategy' AND strategy_options:replication_factor='1';&#60;/p&#62;
&#60;p&#62;&#38;gt; USE a;&#60;br /&#62;
&#38;gt; CREATE TABLE t (id int PRIMARY KEY, col1 text);&#60;/p&#62;
&#60;p&#62;&#38;gt; SELECT * FROM t:&#60;br /&#62;
Unable to complete request: one or more nodes were unavailable.&#60;/p&#62;
&#60;p&#62;&#38;gt; SHOW VERSION;&#60;br /&#62;
[cqlsh 2.2.0 &#124; Cassandra 1.1.5 &#124; CQL spec 3.0.0 &#124; Thrift protocol 19.32.0]&#60;/p&#62;
&#60;p&#62;I'm using DSE, latest release.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>thobbs on "Nodes were Unavailable"</title>
			<link>http://www.datastax.com/support-forums/topic/nodes-were-unavailable/page/2#post-5799</link>
			<pubDate>Fri, 10 Aug 2012 19:11:28 +0000</pubDate>
			<dc:creator>thobbs</dc:creator>
			<guid isPermaLink="false">5799@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Thanks for the post! I sent a note to the docs team, so that should be fixed shortly.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>tstarbow on "Nodes were Unavailable"</title>
			<link>http://www.datastax.com/support-forums/topic/nodes-were-unavailable/page/2#post-5688</link>
			<pubDate>Thu, 09 Aug 2012 17:48:53 +0000</pubDate>
			<dc:creator>tstarbow</dc:creator>
			<guid isPermaLink="false">5688@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;It is pretty annoying that the &#34;Getting Started Using the Cassandra CLI&#34; for Cassandra 1.0 (&#60;a href=&#34;http://www.datastax.com/docs/1.0/dml/using_cql&#34; rel=&#34;nofollow&#34;&#62;http://www.datastax.com/docs/1.0/dml/using_cql&#60;/a&#62;) code doesn't work as written. It looks like it has been fixed on 1.1 docs:&#60;/p&#62;
&#60;p&#62;CREATE KEYSPACE twissandra&#60;br /&#62;
         WITH strategy_class = 'org.apache.cassandra.locator.SimpleStrategy'&#60;br /&#62;
         AND strategy_options:replication_factor='1';
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "ColumnFamilyInputFormat - read and write consistency levels"</title>
			<link>http://www.datastax.com/support-forums/topic/columnfamilyinputformat-read-and-write-consistency-levels#post-858</link>
			<pubDate>Thu, 15 Dec 2011 14:37:13 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">858@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;We were able to try the patch yesterday and we were able to run the hadoop job and read at CL of QUORUM.  Thanks for the help.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>zznate on "ColumnFamilyInputFormat - read and write consistency levels"</title>
			<link>http://www.datastax.com/support-forums/topic/columnfamilyinputformat-read-and-write-consistency-levels#post-827</link>
			<pubDate>Thu, 08 Dec 2011 03:22:35 +0000</pubDate>
			<dc:creator>zznate</dc:creator>
			<guid isPermaLink="false">827@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Ok, looks like you are getting hit by &#60;a href=&#34;https://issues.apache.org/jira/browse/CASSANDRA-3551&#34; rel=&#34;nofollow&#34;&#62;https://issues.apache.org/jira/browse/CASSANDRA-3551&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;If you would like to apply the patch on the source and give it a try, this would actually be super valueable as an external test of the fix.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>zznate on "ColumnFamilyInputFormat - read and write consistency levels"</title>
			<link>http://www.datastax.com/support-forums/topic/columnfamilyinputformat-read-and-write-consistency-levels#post-824</link>
			<pubDate>Wed, 07 Dec 2011 16:46:10 +0000</pubDate>
			<dc:creator>zznate</dc:creator>
			<guid isPermaLink="false">824@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;We are currently looking into this and we'll update here as soon as we find something. Thanks for the extra details and patience.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "ColumnFamilyInputFormat - read and write consistency levels"</title>
			<link>http://www.datastax.com/support-forums/topic/columnfamilyinputformat-read-and-write-consistency-levels#post-823</link>
			<pubDate>Wed, 07 Dec 2011 14:53:16 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">823@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;1.0.5
&#60;/p&#62;</description>
		</item>
		<item>
			<title>zznate on "ColumnFamilyInputFormat - read and write consistency levels"</title>
			<link>http://www.datastax.com/support-forums/topic/columnfamilyinputformat-read-and-write-consistency-levels#post-819</link>
			<pubDate>Wed, 07 Dec 2011 02:13:48 +0000</pubDate>
			<dc:creator>zznate</dc:creator>
			<guid isPermaLink="false">819@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;What version of Cassandra is this? This behavior certainly does not sound correct.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "ColumnFamilyInputFormat - read and write consistency levels"</title>
			<link>http://www.datastax.com/support-forums/topic/columnfamilyinputformat-read-and-write-consistency-levels#post-818</link>
			<pubDate>Tue, 06 Dec 2011 19:54:02 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">818@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;When we run the job and read with consistency level &#34;QUORUM&#34; the cluster's read latency will jump to over a minute, and we see the disk utilization hits 100%.  &#60;/p&#62;
&#60;p&#62;When we run the same job against a keyspace with a replication factor of 1, CL &#34;ONE&#34;, the read latency gets as high as 2 or 3 seconds and the disk utilization doesn't get above 55%.&#60;/p&#62;
&#60;p&#62;Are there settings we can change to help bring down the disk utilization on replicate keyspaces?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "ColumnFamilyInputFormat - read and write consistency levels"</title>
			<link>http://www.datastax.com/support-forums/topic/columnfamilyinputformat-read-and-write-consistency-levels#post-814</link>
			<pubDate>Mon, 05 Dec 2011 21:11:11 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">814@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;The replication factor is set to 3 and we have dropped the batch size ranges as low as 32.  What metrics would you like and is there a way to print a report of the metrics?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>zznate on "ColumnFamilyInputFormat - read and write consistency levels"</title>
			<link>http://www.datastax.com/support-forums/topic/columnfamilyinputformat-read-and-write-consistency-levels#post-813</link>
			<pubDate>Mon, 05 Dec 2011 19:30:25 +0000</pubDate>
			<dc:creator>zznate</dc:creator>
			<guid isPermaLink="false">813@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;What is the replication factor and range batch size? Also, do you have any other metrics for performance of individual nodes? Like what is the OpsCenter output for the nodes when the timeouts occur?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "ColumnFamilyInputFormat - read and write consistency levels"</title>
			<link>http://www.datastax.com/support-forums/topic/columnfamilyinputformat-read-and-write-consistency-levels#post-810</link>
			<pubDate>Mon, 05 Dec 2011 17:18:34 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">810@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;When we run our hadoop job at read consistency &#34;QUORUM&#34; we get a timeout in the ColumnFamilyInputFormat. Our rows really aren’t that big (a few dozen columns @ a few KB per). We have a 4 node cluster running Cassandra 1.0.5.  We have tried setting the timeout to a minute, as well as decreasing the range batch size, but we still end up with the following error:&#60;/p&#62;
&#60;p&#62;java.lang.RuntimeException: TimedOutException()&#60;br /&#62;
	at org.apache.cassandra.hadoop.ColumnFamilyRecordReader$RowIterator.maybeInit(ColumnFamilyRecordReader.java:281)&#60;br /&#62;
	at org.apache.cassandra.hadoop.ColumnFamilyRecordReader$RowIterator.computeNext(ColumnFamilyRecordReader.java:295)&#60;br /&#62;
	at org.apache.cassandra.hadoop.ColumnFamilyRecordReader$RowIterator.computeNext(ColumnFamilyRecordReader.java:183)&#60;br /&#62;
	at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:140)&#60;br /&#62;
	at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:135)&#60;br /&#62;
	at org.apache.cassandra.hadoop.ColumnFamilyRecordReader.nextKeyValue(ColumnFamilyRecordReader.java:139)&#60;br /&#62;
	at org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(MapTask.java:456)&#60;br /&#62;
	at org.apache.hadoop.mapreduce.MapContext.nextKeyValue(MapContext.java:67)&#60;br /&#62;
	at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:143)&#60;br /&#62;
	at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:647)&#60;br /&#62;
	at org.apache.hadoop.mapred.MapTask.run(MapTask.java:32&#60;/p&#62;
&#60;p&#62;Is there something we can check or try and/or change to keep from timing out?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>zznate on "ColumnFamilyInputFormat - read and write consistency levels"</title>
			<link>http://www.datastax.com/support-forums/topic/columnfamilyinputformat-read-and-write-consistency-levels#post-803</link>
			<pubDate>Mon, 05 Dec 2011 01:46:59 +0000</pubDate>
			<dc:creator>zznate</dc:creator>
			<guid isPermaLink="false">803@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;This is best summed up by the following: &#34;Note that if W + R &#38;gt; ReplicationFactor, where W is the number of nodes to block for on write, and R the number to block for on reads, you will have strongly consistent behavior&#34;&#60;/p&#62;
&#60;p&#62;ALL should only be used in situations where high availability is not required.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "ColumnFamilyInputFormat - read and write consistency levels"</title>
			<link>http://www.datastax.com/support-forums/topic/columnfamilyinputformat-read-and-write-consistency-levels#post-800</link>
			<pubDate>Sat, 03 Dec 2011 19:38:25 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">800@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;When running a Hadoop job that uses a Cassandra column family as input, how does setting the read consistency affect the range scan used to get the input?  Ie if we want to guarantee that a hadoop job runs on the most up to date information in a column family, is it better to have written with a consistency level of &#34;ALL&#34; so the job can read with consistency of &#34;ONE&#34; or to both read and write at a consistency level of &#34;QUORUM&#34;?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "Nodes were Unavailable"</title>
			<link>http://www.datastax.com/support-forums/topic/nodes-were-unavailable/page/2#post-765</link>
			<pubDate>Thu, 24 Nov 2011 07:25:41 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">765@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;This is the link I followed : &#60;a href=&#34;http://www.datastax.com/docs/1.0/dml/using_cql&#34; rel=&#34;nofollow&#34;&#62;http://www.datastax.com/docs/1.0/dml/using_cql&#60;/a&#62;.&#60;/p&#62;
&#60;p&#62;Here there is nothing like replcaition factot in the command.&#60;/p&#62;
&#60;p&#62;Thanks,&#60;br /&#62;
Raju.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
