first time user setting up a cluster

Brian Sparrow bsparrow at basho.com
Sat Feb 9 21:28:58 EST 2013


Yeah, it should be more clear in the documentation that once a node has
been started in order to change the name you must either remove the ring
files, reip the node, or riak-admin cluster force-replace the node. Let us
know if you run into any more issues or confusing pieces of documentation.

Thanks!


On Sat, Feb 9, 2013 at 8:49 PM, tech topcis <tech at intrawave.net> wrote:

>  yes, I was following the flow of the documentation.
>
> ## Name of the riak node
> -name riak at 192.168.1.9
>
> I removed four files from /var/lib/riak/ring.
>
> That appears to have worked.
>
> Thank you!
>
>
> On 02/09/2013 04:31 PM, Brian Sparrow wrote:
>
> Did you change the node name in vm.args after the node had been started
> once? Remove the ring file in the riak data directory and start the node
> again.
>
>  -Brian
>
>
> On Sat, Feb 9, 2013 at 11:30 AM, tech topcis <tech at intrawave.net> wrote:
>
>> Hi,
>>
>>    I am following the set-up instructions and ran into a problem when I
>> switched from the loop back ip to the LAN IP.
>>
>>    I followed this page:
>> http://docs.basho.com/riak/1.2.1/cookbooks/Basic-Cluster-Setup/
>>
>>    I was able to edit the two files.  Once I tried to start again, I had
>> an error (below).
>>
>>    Please help me see what I need to change.
>>
>> Thank you, Michael
>>
>> log/console output:
>> Exec: /usr/lib/riak/erts-5.9.1/bin/erlexec -boot
>> /usr/lib/riak/releases/1.2.1/riak             -embedded -config
>> /etc/riak/app.config             -pa
>> /usr/lib/riak/lib/basho-patches             -args_file /etc/riak/vm.args
>> -- console
>> Root: /usr/lib/riak
>> Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:6:6]
>> [async-threads:64] [kernel-poll:true]
>>
>> ** /usr/lib/riak/lib/basho-patches/etop_txt.beam hides
>> /usr/lib/riak/lib/observer-1.1/ebin/etop_txt.beam
>> ** Found 1 name clashes in code paths
>> 10:28:50.822 [info] Application lager started on node 'riak at 192.168.1.9'
>> 10:28:50.904 [info] Upgrading legacy ring
>> 10:28:51.043 [error] gen_server riak_core_capability terminated with
>> reason: no function clause matching orddict:fetch('riak at 192.168.1.9',
>> []) line 72
>> /usr/lib/riak/lib/os_mon-2.2.9/priv/bin/memsup: Erlang has closed.
>>
>> Erlang has closed
>>
>> {"Kernel pid
>>
>> terminated",application_controller,"{application_start_failure,riak_core,{bad_return,{{riak_core_app,start,[normal,[]]},{'EXIT',{{function_clause,[{orddict,fetch,['
>> riak at 192.168.1.9
>> ',[]],[{file,[111,114,100,100,105,99,116,46,101,114,108]},{line,72}]},{riak_core_capability,renegotiate_capabilities,1,[{file,[115,114,99,47,114,105,97,107,95,99,111,114,101,95,99,97,112,97,98,105,108,105,116,121,46,101,114,108]},{line,415}]},{riak_core_capability,handle_call,3,[{file,[115,114,99,47,114,105,97,107,95,99,111,114,101,95,99,97,112,97,98,105,108,105,116,121,46,101,114,108]},{line,208}]},{gen_server,handle_msg,5,[{file,[103,101,110,95,115,101,114,118,101,114,46,101,114,108]},{line,588}]},{proc_lib,init_p_do_apply,3,[{file,[112,114,111,99,95,108,105,98,46,101,114,108]},{line,227}]}]},{gen_server,call,[riak_core_capability,{register,{riak_core,vnode_routing},{capability,[proxy,legacy],legacy,{riak_core,legacy_vnode_routing,[{true,legacy},{false,proxy}]}}},infinity]}}}}}}"}
>>
>> Crash dump was written to: /var/log/riak/erl_crash.dump
>> Kernel pid terminated (application_controller)
>>
>> ({application_start_failure,riak_core,{bad_return,{{riak_core_app,start,[normal,[]]},{'EXIT',{{function_clause,[{orddict,fetch,['
>> riak at 192.168.1.9',[]],
>>
>>
>>
>> _______________________________________________
>> riak-users mailing list
>> riak-users at lists.basho.com
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20130209/81ce1b53/attachment.html>


More information about the riak-users mailing list