hi.
we are trying to run Riak in the Amazon cloud (using OpsWorks).
With every restart of the servers the ip addresses change so using an entry
in the /etc/hosts instead of an IP looks like a great idea.
Google's answer is:
http://lists.basho.com/pipermail/riak-users_lists.basho.com/2011-December
Hey Mike,Another option for your app.config would be to bind everything to "0.0.0.0", which will make Riak listen on all interfaces. This combined with using a domain name in the vm.args should prevent you from having to do renames/changing ips in the config files. If you do this, please consider
It's best ignored, truthfully.
That being said, if you really want to know, there is a good description in
Replication - Understanding Replication by Example [1]
Concepts - Replication [2]
Little Riak Book - Replication and Partitions [3]
[1]:
http://docs.basho.com/riak/latest/theory/concepts/R
Hi Mike,Just to make sure: Riak only supports IP addresses and not DNS names in the config files.Though in your docs it still says:"Riak identifies other machines in the ring using Erlang identifiers (, ex: riak@10.9.8.7)."Riak only accepts ip addresses in the app.config file, but the vm.args "-nam
Is there anywhere a pseudo-code or description of the algorithm how
vnodes (primaries and replicas) would be distributed if I had 3, 4 and more
nodes in the cluster?
Does it depend in any way on the node name or any other setting, or is it
only a function of number of physical nodes?
Regards
Dani
hi.
we are trying to run Riak in the Amazon cloud (using OpsWorks).
With every restart of the servers the ip addresses change so using an entry
in the /etc/hosts instead of an IP looks like a great idea.
Google's answer is:
http://lists.basho.com/pipermail/riak-users_lists.basho.com/2011-December
Dear Alexander, dear Jordan,
Both of your answers proved very helpful, thank you very much. Glad to see an
active mailing list working.
All the best,
PN
> Message du 19/09/13 05:34
> De : "Alexander Sicular"
> A : "pseudo-n...@laposte.net"
> Copie à : "riak-users@lists.basho.com"
> Objet
On September 19, 2013 10:12:06 AM Markus Doppelbauer wrote:
> Hi Alex,
>
> Thanks a lot for your answer.
> Very often (we upgrade an application from BerkeleyDB to RIAK).
>
> E.g.: A new key should be be the largest key + 1. Is there an other
> trick to workaround this problem?
>
> Thanks,
>
You can store revertIndex = (MAX_KEY_VALUE - keyvaluefromberkley) in Riak as
a secondary index for every object. Then get a full range for that index
limiting results to 1. In this way you'll get one result with max
keyvaluefromberkley. Reversing order in a nutshell, because I think values
for 2i i
Hi Alex,
Thanks a lot for your answer.
Very often (we upgrade an application from BerkeleyDB to RIAK).
E.g.: A new key should be be the largest key + 1. Is there an other
trick to workaround this problem?
Thanks,
Markus
Gesendet: Mittwoch, 18. September 2013 um 21:53 Uhr
Von:
10 matches
Mail list logo