Re: Reindexing solr after backup restore
I think I figured it out. I followed this guide: http://docs.basho.com/riak/latest/ops/running/nodes/renaming/#Clusters-from-Backups The first Riak node (changed with riak-admin reip) kept it's Solr index. However, the other nodes when joined via riak-admin cluster force-replace, dropped their Solr indexes. Is this expected? If so, it should really be in the docs, and there should be another way to restore a cluster keeping Solr intact. Also, is there a way to rebuild a Solr index? Thanks, Jason > On 24 Apr 2015, at 15:16, Jason Campbell wrote: > > I've just done a backup and restore of our production Riak cluster, and > Yokozuna has dropped from around 125 million records to 25million. Obviously > the IPs have changed, and although the Riak cluster is stable, I'm not sure > Solr handled the transition as nicely. > > Is there a way to force Solr to rebuild the indexes, or at least get back to > the state it was in before the backup? > > Also, is this expected behaviour? > > Thanks, > Jason > ___ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Reindexing solr after backup restore
I've just done a backup and restore of our production Riak cluster, and Yokozuna has dropped from around 125 million records to 25million. Obviously the IPs have changed, and although the Riak cluster is stable, I'm not sure Solr handled the transition as nicely. Is there a way to force Solr to rebuild the indexes, or at least get back to the state it was in before the backup? Also, is this expected behaviour? Thanks, Jason ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
[riak]compile riak error
Hi, When I make all, got following error: Erlang R16B03, git clone https://github.com/basho/riak git checkout riak-2.0.4 ==> yokozuna (compile) Create dir ../build Pulling Solr from S3 cp: cannot stat ??solr-4.7.0-yz-1.tgz??: No such file or directory ERROR: Command [compile] failed! make: *** [compile] Error 1___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
No WM route
Hi all Im very new to Riak CS so please bear with me! Finally managed to
get Riak, Riak CS and Stanchion all running and now Im trying to add the
admin user. When I run my curl command I get nothing back and in the logs I
see this error:
2015-04-23 11:37:18.024 [error] <0.94.0> No WM route: 'POST' /riak-cs/user
{7,{"user-agent",{'User-Agent',"curl/7.29.0"},{"host",{'Host',"
10.7.2.113:8080
"},{"accept",{'Accept',"*/*"},nil,{"content-type",{'Content-Type',"application/json"},{"content-length",{'Content-Length',"45"},nil,nil},nil}},nil},{"x-rcs-rewrite-path",{"x-rcs-rewrite-path","/riak-cs/user"},{"x-rcs-raw-url",{"x-rcs-raw-url","/riak-cs/user"},nil,nil},nil}}}
I have set anonymous user to on in the riak-cs.conf AS WELL as to true in
the advanced.config. I tried with just in .conf and that didnt work either.
Would anybody have any ideas on how to get this work I would really
appreciate it. Thanks and sorry if Im asking a basic question I just cant
figure it out.
Im running CentOS 7 and:
[root@riakcs riak-cs]# riak version
2.1.0
[root@riakcs riak-cs]# riak-cs version
2.0.0
[root@riakcs riak-cs]# stanchion version
2.0.0
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: scaling up vertically upgrading HD
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 hashing algorithm. The output of sha1 is a number in the > range of 0 to 2^160. That range is partitioned into segments called > "vnodes" in Riak parlance (see ring_size configuration option). Vnodes, or > virtual nodes, in turn are equally allocated to physical machines in the > cluster. Thus, each node in a Riak cluster can be thought of as being > responsible for 1/n of data stored and 1/n performance where n is the > number of machines in the cluster. > > I think I use some more and or better words to describe it here > https://basho.com/why-riak-just-works/ > > -Alexander > > @siculars > http://siculars.posthaven.com > > Sent from my iRotaryPhone > > On Apr 23, 2015, at 10:42, Alex De la rosa > wrote: > > 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 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, >>> >>> 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 >>> Node 4: 500GB >>> Node 5: 750GB >>> >>> In this case riak would make a parity of 500GB per node... so... how >>> could we scale up the HDs? Imagine I want to turn them into the following: >>> >>> Node 1: 1TB >>> Node 2: 1TB >>> Node 3: 1TB >>> Node 4: 1TB >>> Node 5: 1TB >>> >>> How can you rebalance the cluster in the way their partitions grow to >>> fit this new setup? (using Riak 2.1) >>> >>> Thanks, >>> Alex >>> >>> ___ >>> riak-users mailing list >>> riak-users@lists.basho.com >>> >>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >>> >>> >> >> >> -- >> Jon Meredith >> Chief Architect >> Basho Technologies, Inc. >> jmered...@basho.com >> > > ___ > riak-users mailing list > riak-users@lists.basho.com > > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: scaling up vertically upgrading HD
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 partitioned into segments called "vnodes" in Riak parlance (see ring_size configuration option). Vnodes, or virtual nodes, in turn are equally allocated to physical machines in the cluster. Thus, each node in a Riak cluster can be thought of as being responsible for 1/n of data stored and 1/n performance where n is the number of machines in the cluster. I think I use some more and or better words to describe it here https://basho.com/why-riak-just-works/ -Alexander @siculars http://siculars.posthaven.com Sent from my iRotaryPhone > On Apr 23, 2015, at 10:42, Alex De la rosa wrote: > > 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 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, >>> >>> 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 >>> Node 4: 500GB >>> Node 5: 750GB >>> >>> In this case riak would make a parity of 500GB per node... so... how could >>> we scale up the HDs? Imagine I want to turn them into the following: >>> >>> Node 1: 1TB >>> Node 2: 1TB >>> Node 3: 1TB >>> Node 4: 1TB >>> Node 5: 1TB >>> >>> How can you rebalance the cluster in the way their partitions grow to fit >>> this new setup? (using Riak 2.1) >>> >>> Thanks, >>> Alex >>> >>> ___ >>> riak-users mailing list >>> riak-users@lists.basho.com >>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> >> >> >> -- >> Jon Meredith >> Chief Architect >> Basho Technologies, Inc. >> jmered...@basho.com > > ___ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: scaling up vertically upgrading HD
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; 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 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, > > 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 > Node 4: 500GB > Node 5: 750GB > > In this case riak would make a parity of 500GB per node... so... how could we > scale up the HDs? Imagine I want to turn them into the following: > > Node 1: 1TB > Node 2: 1TB > Node 3: 1TB > Node 4: 1TB > Node 5: 1TB > > How can you rebalance the cluster in the way their partitions grow to fit > this new setup? (using Riak 2.1) > > Thanks, > Alex > > ___ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > > > > -- > Jon Meredith > Chief Architect > Basho Technologies, Inc. > jmered...@basho.com > > ___ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: scaling up vertically upgrading HD
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 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, >> >> 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 >> Node 4: 500GB >> Node 5: 750GB >> >> In this case riak would make a parity of 500GB per node... so... how >> could we scale up the HDs? Imagine I want to turn them into the following: >> >> Node 1: 1TB >> Node 2: 1TB >> Node 3: 1TB >> Node 4: 1TB >> Node 5: 1TB >> >> How can you rebalance the cluster in the way their partitions grow to fit >> this new setup? (using Riak 2.1) >> >> Thanks, >> Alex >> >> ___ >> riak-users mailing list >> riak-users@lists.basho.com >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> >> > > > -- > Jon Meredith > Chief Architect > Basho Technologies, Inc. > jmered...@basho.com > ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Re: scaling up vertically upgrading HD
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, > > 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 > Node 4: 500GB > Node 5: 750GB > > In this case riak would make a parity of 500GB per node... so... how could > we scale up the HDs? Imagine I want to turn them into the following: > > Node 1: 1TB > Node 2: 1TB > Node 3: 1TB > Node 4: 1TB > Node 5: 1TB > > How can you rebalance the cluster in the way their partitions grow to fit > this new setup? (using Riak 2.1) > > Thanks, > Alex > > ___ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > -- Jon Meredith Chief Architect Basho Technologies, Inc. jmered...@basho.com ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
scaling up vertically upgrading HD
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 Node 4: 500GB Node 5: 750GB In this case riak would make a parity of 500GB per node... so... how could we scale up the HDs? Imagine I want to turn them into the following: Node 1: 1TB Node 2: 1TB Node 3: 1TB Node 4: 1TB Node 5: 1TB How can you rebalance the cluster in the way their partitions grow to fit this new setup? (using Riak 2.1) Thanks, Alex ___ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
