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 instance, I edited app.config to listen on the local IP address (found using curl http://169.254.169.254/latest/meta-data/local-ipv4) On the first instance, I started riak and was able to ping the node successfully from the local host and from instance two. On the second instance I started riak and then ran the following - http://pastebin.com/CaHH3Eve Each node's vm.args is using the IP address for the `-name` parameter. If you're in a VPC, you may want to check the box for "Enable DNS hostname support for instances launched in this VPC." --- Jeremiah Peschka - Founder, Brent Ozar Unlimited MCITP: SQL Server 2008, MVP Cloudera Certified Developer for Apache Hadoop On Sun, Sep 15, 2013 at 6:39 AM, David Montgomery <[email protected] > wrote: > Its both the fqdn or internal ip address. Either way,,,,same issue riak > refuses to work with ip address or fqdn....and 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 fully qualified domain names (FQDNs) rather than IP addresses for the > cluster member node names. For example, “[email protected]” and “ > [email protected]” are both acceptable node naming schemes, but using the > FQDN style is preferred. > > Once a node has been started, in order to change the name you must either > remove ring files from the data directory, riak-admin > reip<http://docs.basho.com/riak/latest/ops/running/tools/riak-admin/#reip>the > node, or riak-admin > cluster > force-replace<http://docs.basho.com/riak/latest/ops/running/tools/riak-admin/#cluster-force-replace>the > node. > > > > On Sun, Sep 15, 2013 at 9:10 PM, Jeremiah Peschka < > [email protected]> wrote: > >> 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]: >> http://docs.basho.com/riak/latest/ops/building/installing/aws-marketplace/ >> >> >> --- >> Jeremiah Peschka - Founder, Brent Ozar Unlimited >> MCITP: SQL Server 2008, MVP >> Cloudera Certified Developer for Apache Hadoop >> >> >> On Sun, Sep 15, 2013 at 1:06 AM, David Montgomery < >> [email protected]> wrote: >> >>> 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 [email protected] >>> >>> >>> >>> 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 '[email protected]' not responding >>> to pings. >>> >>> When I use 127.0.0.1 and then I run riak start then works. >>> >>> riak start >>> root@ip-10-234-117-74:/etc/riak# riak ping >>> pong >>> >>> >>> I am using m1.large on ubuntu 12.04 and the latest version of riak >>> >>> >>> How does one get past this point? >>> >>> >>> >>> >>> _______________________________________________ >>> riak-users mailing list >>> [email protected] >>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >>> >>> >> >> _______________________________________________ >> riak-users mailing list >> [email protected] >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> >> >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
