Re: Decommissioning node is causing broken pipe error

2011-05-05 Thread Peter Schuller
It's no longer recommended to run nodetool compact regularly as it can mean that some tombstones do not get to be purged for a very long time. I think this is a mis-typing; it used to be that major compactions were necessary to remove tombstones, but this is no longer the case in 0.7 so that

Re: Decommissioning node is causing broken pipe error

2011-05-05 Thread Tyler Hobbs
On Thu, May 5, 2011 at 1:21 AM, Peter Schuller peter.schul...@infidyne.comwrote: It's no longer recommended to run nodetool compact regularly as it can mean that some tombstones do not get to be purged for a very long time. I think this is a mis-typing; it used to be that major compactions

Re: Decommissioning node is causing broken pipe error

2011-05-05 Thread aaron morton
Yes that was what I was trying to say. thanks - Aaron Morton Freelance Cassandra Developer @aaronmorton http://www.thelastpickle.com On 5 May 2011, at 18:52, Tyler Hobbs wrote: On Thu, May 5, 2011 at 1:21 AM, Peter Schuller peter.schul...@infidyne.com wrote: It's no longer

Re: Decommissioning node is causing broken pipe error

2011-05-05 Thread Sameer Farooqui
Just wanted to update you guys that we turned on DEBUG level logging on the decommissioned node and the node receiving the decommissioned node's range. We did this by editing cassandra-home/conf/log4j-server.properties and changing the log4j.rootLogger to DEBUG. We ran decommission again and saw

Re: Decommissioning node is causing broken pipe error

2011-05-05 Thread aaron morton
Could you provide some of the log messages when the receiver ran out of disk space ? Sounds like it should be at ERROR level. Thanks - Aaron Morton Freelance Cassandra Developer @aaronmorton http://www.thelastpickle.com On 6 May 2011, at 09:16, Sameer Farooqui wrote: Just

RE: Decommissioning node is causing broken pipe error

2011-05-05 Thread tamara.alexander
been nice to get an error regardless. Thanks again for your help! From: aaron morton [mailto:aa...@thelastpickle.com] Sent: Thursday, May 05, 2011 4:54 PM To: user@cassandra.apache.org Subject: Re: Decommissioning node is causing broken pipe error Could you provide some of the log messages when

Re: Decommissioning node is causing broken pipe error

2011-05-04 Thread aaron morton
It's no longer recommended to run nodetool compact regularly as it can mean that some tombstones do not get to be purged for a very long time. Minor compaction is all you need to keep things in check, however 648 seems like a lot of SSTables. Were some of these compacted files ? How many

Decommissioning node is causing broken pipe error

2011-05-03 Thread tamara.alexander
Hi all, I ran decommission on a node in my 32 node cluster. After about an hour of streaming files to another node, I got this error on the node being decommissioned: INFO [MiscStage:1] 2011-05-03 21:49:00,235 StreamReplyVerbHandler.java (line 58) Need to re-stream file