That is entirely the problem.
By having one node, but RF=3, you have created this exact problem.
Each node can own, at most, one copy of each row of data, so the cluster
is treating this (correctly) as a degraded runtime environment where no
operation requiring CL > 1 will always fail. LWT requires quorum #of nodes
to be available.
-Tupshin
On Apr 16, 2014 5:45 AM, "Vivek Mishra" <mishra.v...@gmail.com> wrote:
> Hi,
> Mine is a simple case. Running on single node only. Keyspace is:
>
> create keyspace twitter with replication = {'class':'SimpleStrategy',
> 'replication_factor' : 3}
>
> -Vivek
>
>
> On Wed, Apr 16, 2014 at 1:27 AM, Tupshin Harper <tups...@tupshin.com>wrote:
>
>> Please provide your keyspace definition, and the output of "nodetool
>> ring"
>>
>> -Tupshin
>> On Apr 15, 2014 3:52 PM, "Vivek Mishra" <mishra.v...@gmail.com> wrote:
>>
>>> Hi,
>>> I am trying Cassandra light weight transaction support with Cassandra
>>> 2.0.4
>>>
>>> cqlsh:twitter> create table user(user_id text primary key, namef text);
>>> cqlsh:twitter> insert into user(user_id,namef) values('v','ff') if not
>>> exists;
>>>
>>> *Unable to complete request: one or more nodes were unavailable.*
>>>
>>> Any suggestions?
>>>
>>> -Vivek
>>>
>>
>
