Re: JBOD device space allocation?

On Wed, Feb 24, 2016 at 6:28 PM, Jack Krupansky wrote: > Thanks. I didn't pay enough attention to that statement on my initial > reading of that post (which was where I became aware of the 3.2 behavior in > the first place.) > > Considering that the doc explicitly

Re: JBOD device space allocation?

Thanks. I didn't pay enough attention to that statement on my initial reading of that post (which was where I became aware of the 3.2 behavior in the first place.) Considering that the doc explicitly recommends that the byte ordered partitioner not be used, that implies that the 3.2 JBOD behavior

Re: JBOD device space allocation?

If you don't use RandomPartitioner/Murmur3Partitioner you will get the old behavior. On Wed, Feb 24, 2016 at 2:47 AM, Jack Krupansky wrote: > I just wanted to confirm whether my understanding of how JBOD allocates > device space is correct of not... > > Pre-3.2: > On

Re: JBOD device space allocation?

It is mentioned here btw: http://www.datastax.com/dev/blog/improving-jbod On Wed, Feb 24, 2016 at 8:14 AM, Marcus Eriksson wrote: > If you don't use RandomPartitioner/Murmur3Partitioner you will get the old > behavior. > > On Wed, Feb 24, 2016 at 2:47 AM, Jack Krupansky

JBOD device space allocation?

I just wanted to confirm whether my understanding of how JBOD allocates device space is correct of not... Pre-3.2: On each memtable flush Cassandra will select the directory (device) which has the most available space as a percentage of the total available space on all of the listed