Re: Riak and ec2 with vm.args - Node 'r...@ip-10-234-117-74.eu-west-1.compute.internal' not responding to pings.

2013-09-15 Thread Hector Castro
VPC is not a requirement, although it is definitely recommended for greenfield projects. --  Hector On September 16, 2013 at 12:46:10 AM, David Montgomery (davidmontgom...@gmail.com) wrote: I am not using VPC.  Is using VPC required? On Mon, Sep 16, 2013 at 12:16 AM, Jeremiah Peschka wro

Re: Riak and ec2 with vm.args - Node 'r...@ip-10-234-117-74.eu-west-1.compute.internal' not responding to pings.

2013-09-15 Thread David Montgomery
I am not using VPC. Is using VPC required? On Mon, Sep 16, 2013 at 12:16 AM, Jeremiah Peschka < jeremiah.pesc...@gmail.com> wrote: > Welp, here's what I did and it seemed to work for me: > > Created a new VPC > Created a subnet in said VPC > Created a default route for SSH connectivity > Crea

Re: Riak and ec2 with vm.args - Node 'r...@ip-10-234-117-74.eu-west-1.compute.internal' not responding to pings.

2013-09-15 Thread Hector Castro
Hey David, I created a m1.small Ubuntu 12.04 x64 instance within EC2-Classic and executed the following commands on it: https://gist.github.com/hectcastro/6576714 Please take a look to see if I did anything differently. --  Hector On September 15, 2013 at 12:18:25 PM, Jeremiah Peschka (jerem

Re: new cluster -- riak starts and dies on each vm.

2013-09-15 Thread Eric Redmond
Fwiw, that link is old, and should have redirected. The new perf tuning doc is here. http://docs.basho.com/riak/latest/ops/tuning/linux/ Eric On Sep 15, 2013 10:56 AM, "Evan Vigil-McClanahan" wrote: > Riak is no longer built or tested on 32 bit machines, so that could > potentially be a problem

Re: new cluster -- riak starts and dies on each vm.

2013-09-15 Thread Evan Vigil-McClanahan
Riak is no longer built or tested on 32 bit machines, so that could potentially be a problem. This document has some recommendations on tunings for linux that can affect the OOM killer and VM system, most notably the vm.swappiness sysctl: http://docs.basho.com/riak/latest/cookbooks/Linux-Performan

Re: Riak and ec2 with vm.args - Node 'r...@ip-10-234-117-74.eu-west-1.compute.internal' not responding to pings.

2013-09-15 Thread Jeremiah Peschka
Welp, here's what I did and it seemed to work for me: Created a new VPC Created a subnet in said VPC Created a default route for SSH connectivity Created a security group with the TCP/IP settings outline in the AWS PDF Created two instances using the Riak AMI, both inside the VPC. On each instanc

new cluster -- riak starts and dies on each vm.

2013-09-15 Thread Daniel Rathbone
I'm setting up a new small riak cluster - 8 VMs, 4GB each. Riak starts and dies after a few seconds on each VM. I'd like to figure out why. I'm running riak 1.4.1, built from source on ubuntu 12.04 (32 bit). I have AAE and search turned off and my backend is set to leveldb. Ring size is 64. All th

Re: secondary index issue

2013-09-15 Thread Jeremiah Peschka
While I can't say for sure, what I suspect is happening is that the escape character is being ignored and you're getting a query for a range. Both the original and the range query produce the same result: # original $ curl http://127.0.0.1:10018/buckets/youmag/index/contentid_bin/1570\/204004 {"ke

secondary index issue

2013-09-15 Thread Fabrice Sznajderman
Hello, I a new comer on Riak. I started to work with it and i faced with a strange behavior in case of secondary index. First of all I added many objects into RIak with the following queries : curl -XPUT -H 'x-riak-index-contentid_bin: '1641/199095'' -H 'Content-Type: application/json' -d '{

Re: Riak and ec2 with vm.args - Node 'r...@ip-10-234-117-74.eu-west-1.compute.internal' not responding to pings.

2013-09-15 Thread David Montgomery
Its both the fqdn or internal ip address. Either waysame issue riak refuses to work with ip address or fqdnand I dont know why. on bash page the recommend using fqdn which adds to tbhe confusion http://docs.basho.com/riak/latest/ops/building/basic-cluster-setup/ *Node Names* Use ful

Re: Riak and ec2 with vm.args - Node 'r...@ip-10-234-117-74.eu-west-1.compute.internal' not responding to pings.

2013-09-15 Thread Jeremiah Peschka
Starting on page 3, the Riak on AWS [1] whitepaper has some instructions on getting things set up. In the docs, they recommend using the AWS internal IP address instead of the FQDN. This advice is also repeated in the Riak wiki [2]. [1]: http://media.amazonwebservices.com/AWS_NoSQL_Riak.pdf [2]:

Riak and ec2 with vm.args - Node 'r...@ip-10-234-117-74.eu-west-1.compute.internal' not responding to pings.

2013-09-15 Thread David Montgomery
Hi, I am having a very difficult time installing riak on ec2. To start ...I cant get past using private ip address or private dns when setting vm.args -name riak@127.0.0.1 root@ip-10-234-117-74:/home/ubuntu# hostname --fqdn ip-10-234-117-74.eu-west-1.compute.internal riak start riak ping Node