On Fri, Mar 23, 2012 at 6:54 AM, Peter Schuller wrote:
> > You would have to iterate through all sstables on the system to repair
> one
> > vnode, yes: but building the tree for just one range of the data means
> that
> > huge portions of the sstables files can be skipped. It should scale down
>
> You would have to iterate through all sstables on the system to repair one
> vnode, yes: but building the tree for just one range of the data means that
> huge portions of the sstables files can be skipped. It should scale down
> linearly as the number of vnodes increases (ie, with 100 vnodes, it
>
> Does the new scheme still require the node to re-iterate all sstables to
> build the merkle tree or streaming data for partition level
> repair and move?
You would have to iterate through all sstables on the system to repair one
vnode, yes: but building the tree for just one range of the data
On Thu, Mar 22, 2012 at 6:20 PM, Richard Low wrote:
> On 22 March 2012 05:48, Zhu Han wrote:
>
> > I second it.
> >
> > Is there some goals we missed which can not be achieved by assigning
> > multiple tokens to a single node?
>
> This is exactly the proposed solution. The discussion is about h
On 22 March 2012 05:48, Zhu Han wrote:
> I second it.
>
> Is there some goals we missed which can not be achieved by assigning
> multiple tokens to a single node?
This is exactly the proposed solution. The discussion is about how to
implement this, and the methods of choosing tokens and replica
