for doing the shuffle, we
aren't able to enable shuffling on the other 4 nodes in the cluster.
We get the error message 'Failed to enable shuffling', which looks to
be a generic string printed when a JMX IOException is caught.
Unfortunately, the underlying error is not printed so I'm effectively
On Mon, Sep 8, 2014 at 11:19 AM, Robert Coli rc...@eventbrite.com wrote:
On Mon, Sep 8, 2014 at 11:08 AM, Tim Heckman t...@pagerduty.com wrote:
I'm looking to convert our recently upgraded Cassandra cluster from a
single token per node to using vnodes. We've determined that based on
our data
On Mon, Sep 8, 2014 at 1:21 PM, Tim Heckman t...@pagerduty.com wrote:
We're still at the exploratory stage on systems that are not
production-facing but contain production-like data. Based on our
placement strategy we have some concerns that the new datacenter
approach may be riskier or more
I believe shuffle has been removed recently. I do not recommend using
it for any reason.
If you really want to go vnodes, your only sane option is to add a new
DC that uses vnodes and switch to it.
The downside in the 2.0.x branch to using vnodes is that repairs take
N times as long, where N is
On Mon, Sep 8, 2014 at 1:45 PM, Jonathan Haddad j...@jonhaddad.com wrote:
I believe shuffle has been removed recently. I do not recommend using
it for any reason.
We're still using the 1.2.x branch of Cassandra, and will be for some
time due to the thrift deprecation. Has it only been removed
Thrift is still present in the 2.0 branch as well as 2.1. Where did
you see that it's deprecated?
Let me elaborate my earlier advice. Shuffle was removed because it
doesn't work for anything beyond a trivial dataset. It is definitely
more risky than adding a new vnode enabled DC, as it does
On Mon, Sep 8, 2014 at 2:01 PM, Tim Heckman t...@pagerduty.com wrote:
We're still using the 1.2.x branch of Cassandra, and will be for some
time due to the thrift deprecation. Has it only been removed from the
2.x line?
Other than the fact that 2.0.x is not production ready yet, there's no
