Re: Drop/Create table with same CF Name

2015-05-26 Thread Ken Hancock
Nate, how does this get around the issue? I'm guessing that just extends the timeout, but if I had a server failure such that the server was down for a couple hours, truncate would still have issues? On Sat, May 23, 2015 at 5:46 PM, Nate McCall n...@thelastpickle.com wrote: Truncate would

Re: Drop/Create table with same CF Name

2015-05-26 Thread Nate McCall
You should not run a truncate until the whole ring is reporting Up/Normal. If there is a lot of flapping and it's a critical situation, disable hinted handoff as well (and you may want to move phi_convict_threshold up to 16 as well temporarily). Stopping the compaction process temporarily on

RE: Drop/Create table with same CF Name

2015-05-25 Thread Walsh, Stephen
Totally agree with this. From: Ken Hancock [mailto:ken.hanc...@schange.com] Sent: 22 May 2015 17:10 To: user@cassandra.apache.org Subject: Re: Drop/Create table with same CF Name This issue really needs to be strongly highlighted in the documentation. Imagine someone noticing similarities

Re: Drop/Create table with same CF Name

2015-05-23 Thread Nate McCall
Truncate would have been the tool of choice, however my understanding is truncate fails unless all nodes are up and running which makes it a non-workable choice since we can't determine when failures will occur. You can get around this via: - in cassandra.yaml, turning up

RE: Drop/Create table with same CF Name

2015-05-22 Thread Walsh, Stephen
To: user@cassandra.apache.org Subject: Re: Drop/Create table with same CF Name Thanks Mark (though that article doesn't appear publicly accessible for others). Truncate would have been the tool of choice, however my understanding is truncate fails unless all nodes are up and running which makes it a non

Re: Drop/Create table with same CF Name

2015-05-22 Thread Ken Hancock
@cassandra.apache.org *Subject:* Re: Drop/Create table with same CF Name Thanks Mark (though that article doesn't appear publicly accessible for others). Truncate would have been the tool of choice, however my understanding is truncate fails unless all nodes are up and running which makes

Re: Drop/Create table with same CF Name

2015-05-22 Thread Sebastian Estevez
17:13 *To:* user@cassandra.apache.org *Subject:* Re: Drop/Create table with same CF Name Thanks Mark (though that article doesn't appear publicly accessible for others). Truncate would have been the tool of choice, however my understanding is truncate fails unless all nodes are up

RE: Drop/Create table with same CF Name

2015-05-22 Thread Walsh, Stephen
@cassandra.apache.orgmailto:user@cassandra.apache.org Subject: Re: Drop/Create table with same CF Name Thanks Mark (though that article doesn't appear publicly accessible for others). Truncate would have been the tool of choice, however my understanding is truncate fails unless all nodes are up

Re: Drop/Create table with same CF Name

2015-05-22 Thread Ken Hancock
May 2015 14:46 *To:* user@cassandra.apache.org *Subject:* Re: Drop/Create table with same CF Name I’m aware of issues where recreating key spaces can cause inconsistency in 2.0.13 if memTables are not flushed beforehand , is this the issues that is resolved? Yep, that's https

Re: Drop/Create table with same CF Name

2015-05-21 Thread Mark Reddy
Yes, it's a known issue. For more information on the topic see this support post from DataStax: https://support.datastax.com/hc/en-us/articles/204226339-How-to-drop-and-recreate-a-table-in-Cassandra-versions-older-than-2-1 Mark On 21 May 2015 at 15:31, Ken Hancock ken.hanc...@schange.com wrote:

Re: Drop/Create table with same CF Name

2015-05-21 Thread Ken Hancock
Thanks Mark (though that article doesn't appear publicly accessible for others). Truncate would have been the tool of choice, however my understanding is truncate fails unless all nodes are up and running which makes it a non-workable choice since we can't determine when failures will occur. Ken