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 <maxi...@trackstudio.com> 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, 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: >> >> What does JMX report as described in >> http://wiki.apache.org/cassandra/Streaming ? >> >> 2010/5/19 Maxim Kramarenko<maxi...@trackstudio.com>: >>> >>> 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, like >>> get MailArchive.Meta['ec3-n2:1274046482!5C/9B-05558-11860FB4!c'] >>> >>> on node 1 and 3 all works fine, but node 2 cli always return >>> Exception null >>> >>> data is 3 days old, so it doesn't seems like temp effect. >>> >>> No errors in log. >>> Node 2 restart doesn't help too. >>> tpstats returns 0 active/pending in all rows. >>> >>> What is it ? >>> >> >> >> > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
