Re: scaling up vertically upgrading HD

2015-04-23 Thread Alex De la rosa
Awesome! Thank you very much :) On Thursday, April 23, 2015, Alexander Sicular wrote: > Hi Alex! > > Yes, each node would use an even amount of space regardless of maximum > disk space available. > > The "evenness" has to do with Riak's uniform data distribution due to the > sha1 consistent hash

Re: scaling up vertically upgrading HD

2015-04-23 Thread Alexander Sicular
Hi Alex! Yes, each node would use an even amount of space regardless of maximum disk space available. The "evenness" has to do with Riak's uniform data distribution due to the sha1 consistent hashing algorithm. The output of sha1 is a number in the range of 0 to 2^160. That range is partition

Re: scaling up vertically upgrading HD

2015-04-23 Thread John Daily
Riak does not currently try to protect you against dumping 2 gallons of water in a 1 gallon jug, so each node will write data until it can’t. -John On Apr 23, 2015, at 10:42 AM, Alex De la rosa wrote: > Cool, thank you :) however, is true that if 4 nodes are 1TB and the other one > is 2TB; th

Re: scaling up vertically upgrading HD

2015-04-23 Thread Alex De la rosa
Cool, thank you :) however, is true that if 4 nodes are 1TB and the other one is 2TB; the 5 nodes will act as having 1TB each, right? (I guess that's what you mean with "Riak allocates data to nodes evenly") Thanks, Alex On Thu, Apr 23, 2015 at 4:40 PM, Jon Meredith wrote: > Hi Alex, > > Riak a

Re: scaling up vertically upgrading HD

2015-04-23 Thread Jon Meredith
Hi Alex, Riak allocates data to nodes evenly - it doesn't take into account free space. You should just be able to upgrade all nodes to 1Tb and Riak will use the space, without needing to take any additional actions. Jon On Thu, Apr 23, 2015 at 7:17 AM, Alex De la rosa wrote: > Hi there, > >

scaling up vertically upgrading HD

2015-04-23 Thread Alex De la rosa
Hi there, I have the following question about scaling up vertically upgrading HDs to get more space. I have the understanding that if HDs are of different sizes on ring creation, they get the smallest size of them all and make all nodes even, for example: Node 1: 500GB Node 2: 500GB Node 3: 750GB