Re: Strange error with data reading

2010-05-20 Thread Jonathan Ellis
yes, the extra io + cpu caused by decomission will affect reads (and writes, to a lesser degree) On Thu, May 20, 2010 at 10:18 AM, Maxim Kramarenko wrote: > It reports, that node 3 transfer data to node 1. As I remember, node 2 > doesn't send or receive data. > > BTW, after a few hrs (probably, a

Re: Strange error with data reading

2010-05-20 Thread Maxim Kramarenko
It reports, that node 3 transfer data to node 1. As I remember, node 2 doesn't send or receive data. BTW, after a few hrs (probably, after decomission finished), node 2 become work again, without restart. Can decommission of node 3 affect reading ? On 20.05.2010 18:51, Jonathan Ellis wrote:

Re: Strange error with data reading

2010-05-20 Thread Jonathan Ellis
What does JMX report as described in http://wiki.apache.org/cassandra/Streaming ? 2010/5/19 Maxim Kramarenko : > Hello! > > I have 3 node cluster: node1, node2, node3. Replication factor = 2. > I run decommission on node3 and it's in progress, moving data to node1 > > Ring on all nodes show all 3

Strange error with data reading

2010-05-19 Thread Maxim Kramarenko
Hello! I have 3 node cluster: node1, node2, node3. Replication factor = 2. I run decommission on node3 and it's in progress, moving data to node1 Ring on all nodes show all 3 nodes up, no problems (but node 1 response with 3-5 sec delay). I tried to execute a few "get" statements using cli, l