Re: Replace Live Node

2011-09-13 Thread Kyle Gibson
Just wanted to update and say the move was completed without any issues in v 0.7.8. Thanks for all the help everyone. On Mon, Sep 12, 2011 at 4:31 PM, Jeremy Hanna wrote: >> So to move data from node with token 0, the new node needs to have >> initial token set to 17014118346046923173168730371588

Re: Replace Live Node

2011-09-12 Thread Kyle Gibson
^127 - 1, which is > 170141183460469231731687303715884105727 > On Sep 12, 2011, at 2:30 PM, Kyle Gibson wrote: > >> What could you do if the initial_token is 0? >> >> On Mon, Sep 12, 2011 at 1:09 PM, Jeremy Hanna >> wrote: >>> Yeah - I would bootstrap

Re: Replace Live Node

2011-09-12 Thread Kyle Gibson
ore 0.8.3.  Use decommission if you can if you're > dealing with a live node. > > On Sep 12, 2011, at 10:42 AM, Kyle Gibson wrote: > >> Version=0.7.8 >> >> I have a 3 node cluster with RF=3, how would I move data from a live >> node to a replacement node? >&

Replace Live Node

2011-09-12 Thread Kyle Gibson
Version=0.7.8 I have a 3 node cluster with RF=3, how would I move data from a live node to a replacement node? I tried an autobootstrap + decomission, but I got this error on the live node: Exception in thread "main" java.lang.IllegalStateException: replication factor (3) exceeds number of endpo

Re: Occasionally getting old data back with ConsistencyLevel.ALL

2011-08-28 Thread Kyle Gibson
Thanks for the reply Peter, you may have discovered the problem, I'll explain below. On Sun, Aug 28, 2011 at 8:51 AM, Peter Schuller wrote: >> Understood. In the code example I provided, I am writing the same >> value, but I am doing so in quick succession, so perhaps a few second >> sleep might

Re: Occasionally getting old data back with ConsistencyLevel.ALL

2011-08-26 Thread Kyle Gibson
through, and the same IPN was processed twice. Does anyone have any more suggestions as to what is going on here? On Mon, Aug 22, 2011 at 1:59 PM, Kyle Gibson wrote: > Thanks for the reply. > > On Mon, Aug 22, 2011 at 1:11 PM, Dominic Williams > wrote: >> Hi there, here&#

Re: Occasionally getting old data back with ConsistencyLevel.ALL

2011-08-22 Thread Kyle Gibson
er. This is how I know for sure the event is being processed twice, because not only do I receive two emails (spaced 5 minutes apart) but does the individual who paid. This is often embarrassing to explain and somewhat difficult, customers get confused as to which account they are supposed to u

Re: Occasionally getting old data back with ConsistencyLevel.ALL

2011-08-22 Thread Kyle Gibson
I made some changes to my code base that uses cassandra. I went back to using the "processed" column, but instead of using "0" or "1" I decided to use "no" and "yes" You can view the code here: http://pastebin.com/gRBC16e7 As you can see from the code, I perform an insert, get, check the result,

Re: Occasionally getting old data back with ConsistencyLevel.ALL

2011-08-19 Thread Kyle Gibson
The cron script doesn't do much. It pulls new IPNs (usually only 1 in a given 5 minute period), inserts a row, and then sends an email. As for failure handling in the script itself, I rely on python exception handling, and whenever an exception occurs I do get an email with the exception details.

Occasionally getting old data back with ConsistencyLevel.ALL

2011-08-18 Thread Kyle Gibson
I am running cassandra 0.7.8. pycassa 1.1.0 Nodes=7, RF=3 This problem started a few months ago and only occurs sporadically. I receive notifications from paypal's IPN. The IPN data is saved into a column family. I add another column for "processed" which is set to 0. Every 5 minutes, a cron sc

phpcassa occasional Not Found Exception

2011-08-07 Thread Kyle Gibson
Cassandra: 0.7.8 phpcassa: 0.7.a.4 The front page of a site I manage displays a list of products available. If a product is available, a visitor can order, otherwise "not in stock" is displayed. Whether the product is in stock or not is determined from the cassandra cluster. Occasionally, but not

Re: Replicating to all nodes

2011-07-15 Thread Kyle Gibson
> The node (known as the "coordinating node" because it co-ordinates the > request submitted by the client) will send the request to the nodes > that are in the replica set for the row. The client need not care > about which host it connects to, other than that it be "one of the > ones in the corre

Re: Replicating to all nodes

2011-07-15 Thread Kyle Gibson
> No. I am not entirely sure from where the confusion comes, so I will > just try to summarize things from scratch in a brief manner. > > Any piece of data you store in Cassandra is going to be in a > particular row, which has a row key. > > That row will have a "replica set" in the Cassandra clust

Re: Replicating to all nodes

2011-07-15 Thread Kyle Gibson
So my understanding of how cassandra saves data is incorrect. I was/am under the impression that a node owns a particular token range, and does not save any data that falls outside of that range (with exception to any data that might be replicated to it). Based on what you are saying, each node ow

Re: Replicating to all nodes

2011-07-13 Thread Kyle Gibson
Thanks for the reply Peter. The goal is to configure a cluster in which reads and writes can complete successfully even if only 1 node is online. For this to work, each node would need the entire dataset. Your example of a 3 node ring with RF=3 would satisfy this requirement. However, if two nodes

Replicating to all nodes

2011-07-13 Thread Kyle Gibson
I am wondering if the following cluster figuration is possible with cassandra, and if so, how it could be achieved. Please also feel free to point out any issues that may make this configuration undesired that I may not have thought of. Suppose a cluster of N nodes. Each node replicates the data

AssertionError: No data found for NamesQueryFilter

2011-07-12 Thread Kyle Gibson
Running version 0.7.6-2, recently upgraded from 0.7.3. I am get a time out exception when I run a particular get_indexed_slices, which results in the following error showing up on a few nodes: ERROR [ReadStage:16] 2011-07-12 23:01:31,424 AbstractCassandraDaemon.java (line 114) Fatal exception in