amazon - Riak "Node is not reachable" -


i using riak 2.1.4 series in amazon. totally new , have couple of questions :

  1. i deployed instance of riak. deployed in ec2 instance ?
  2. do need app.config , vm.args files riak configuration. think if nodename available in riak.conf thats enough isnt ?
  3. i see ip address of instance different once configured in riak.conf fine ? i.e nodename example instance name ec2-35-160-xxx-xx.us-west-2.compute.amazonaws.com , riak.conf has riak@172.31.xx.xx

only change in riak.conf

ring_size = 64  erlang.distribution.port_range.minimum = 6000 erlang.distribution.port_range.maximum = 7999  transfer_limit = 2 search = on 

this configuration exists in each instance. missing here ? can give sample configuration 5 node cluster ?

kindly me resolve issue.

  1. i deployed instance of riak. deployed in ec2 instance ?

not sure asking here

  1. do need app.config , vm.args files riak configuration. think if nodename available in riak.conf thats enough isnt ?

the 'app.config' , 'vm.args' files old way configure riak. 'riak.conf' , 'advanced.config' files new way. old way still accepted, support legacy installations, expect support dropped in future release. see http://docs.basho.com/riak/kv/2.1.4/configuring/basic/

  1. i see ip address of instance different once configured in riak.conf fine ? i.e nodename example instance name ec2-35-160-xxx-xx.us-west-2.compute.amazonaws.com , riak.conf has riak@172.31.xx.xx

in general, if want erlang nodes communicate must able locate each other using node name. node name uses local@domain pattern. other nodes must able resolve domain part ip address valid machine node running on, , node register local part local erlang port mapper daemon(epmd).

so whether or not riak@172.31.x.x valid node name depend on cluster's other nodes' ability reach private address.

most riak-admin commands spawn second maintenance node locally, uses remote procedure calls talk running riak instance. if 172.31.x.x ip address not assigned local machine, riak-admin commands fail find node talk to.


Comments

Popular posts from this blog

java - SSE Emitter : Manage timeouts and complete() -

jquery - uncaught exception: DataTables Editor - remote hosting of code not allowed -

java - How to resolve error - package com.squareup.okhttp3 doesn't exist? -