Re: [EXTERNAL] Re: Increasing VNodes

t; > > > > *From:* Jon Haddad [mailto:jonathan.had...@gmail.com] * On Behalf Of *Jon > Haddad > *Sent:* Wednesday, October 04, 2017 10:27 AM > *To:* user > *Subject:* [EXTERNAL] Re: Increasing VNodes > > > > The site (with the docs) is probably more helpful to l

RE: [EXTERNAL] Re: Increasing VNodes

Email : kishore.mohapa...@nuance.com<mailto:kishore.mohapa...@nuance.com> From: Jon Haddad [mailto:jonathan.had...@gmail.com] On Behalf Of Jon Haddad Sent: Wednesday, October 04, 2017 10:27 AM To: user Subject: [EXTERNAL] Re: Increasing VNodes The site (with the docs) is probably more h

Re: Increasing VNodes

The site (with the docs) is probably more helpful to learn about how reaper works: http://cassandra-reaper.io/ > On Oct 4, 2017, at 9:54 AM, Chris Lohfink wrote: > > Increasing number of tokens will make repairs worse not better. You can just > split the sub range

Re: Increasing VNodes

Increasing number of tokens will make repairs worse not better. You can just split the sub ranges into smaller chunks, you dont need to use vnodes to do that. Simple approach is to iterate through each host token range and split by N and repair them (ie https://github.com/onzra/cassandra_range_repa

Re: Increasing VNodes

You don't need to change the number of vnodes, you can manually select CONTAINED token subranges and pass in -st and -et (just try to pick a number > 2^20 that is fully contained by at least one vnode). On Wed, Oct 4, 2017 at 9:46 AM, Mohapatra, Kishore < kishore.mohapa...@nuance.com> wrote: >

Increasing VNodes

Hi, We are having a lot of problems in repair process. We use sub range repair. But most of the time, some ranges fails with streaming error or some other kind of error. So wondering if it will help if we increase the no. of VNodes from 256 (default) to 512. But increasing the VNodes wil