2017-01-11 44 views
0

我们所有的erlang节点只监听他们的私有地址。随着1了Riak,我们用来添加下列app.config一个类似于到:限制riak2监听的地址(内核,{inet_dist_use_interface,inet:ip_address()})

{kernel, [   
      {inet_dist_use_interface, {192,168,0,42}}, 

这似乎不再是可能的了Riak 2. riak.conf不允许任意应用程序参数。所以我给vm.args一个镜头:

-kernel inet_dist_use_interface '{192,168,0,42}' 

这反过来,引起以下错误:

{application_start_failure,             
    riak_core,                 
    {bad_return,                 
    {{riak_core_app,start,[normal,[]]},           
    {'EXIT',                 
     {{function_clause,              
     [{orddict,                
      fetch,                
      [[email protected],              
      [{'[email protected]',            
      [{{riak_control,member_info_version},[v1,v0]},      
       {{riak_core,bucket_types},[true,false]},       
       {{riak_core,fold_req_version},[v2,v1]},       
       {{riak_core,net_ticktime},[true,false]},       
       {{riak_core,resizable_ring},[true,false]},      
       {{riak_core,security},[true,false]},        
       {{riak_core,staged_joins},[true,false]},       
       {{riak_core,vnode_routing},[proxy,legacy]},      
       {{riak_kv,anti_entropy},[enabled_v1,disabled]},     
       {{riak_kv,crdt},             
       [[pncounter,riak_dt_pncounter,riak_dt_orswot,riak_dt_map],  
       [pncounter],             
       []]},               
       {{riak_kv,crdt_epoch_versions},         
       [[{riak_dt_map,2},{riak_dt_orswot,2},{riak_dt_pncounter,2}],  
       [{riak_dt_pncounter,2}]]},          
       {{riak_kv,handoff_data_encoding},[encode_raw,encode_zlib]},  
       {{riak_kv,index_backpressure},[true,false]},      
       {{riak_kv,legacy_keylisting},[false]},       
       {{riak_kv,listkeys_backpressure},[true,false]},     
       {{riak_kv,mapred_2i_pipe},[true,false]},       
       {{riak_kv,mapred_system},[pipe]},         
       {{riak_kv,object_format},[v1,v0]},        
       {{riak_kv,put_fsm_ack_execute},[enabled,disabled]},    
       {{riak_kv,secondary_index_version},[v3,v2,v1]},     
       {{riak_kv,vclock_data_encoding},[encode_zlib,encode_raw]},  
       {{riak_kv,vnode_vclocks},[true,false]},       
       {{riak_pipe,trace_format},[ordsets,sets]}]}]],     
      [{file,"orddict.erl"},{line,72}]},         
     {riak_core_capability,renegotiate_capabilities,1,[{file,"src/riak_core_capability.erl"},{line,441}]}, 
     {riak_core_capability,handle_call,3,[{file,"src/riak_core_capability.erl"},{line,213}]}, 
     {gen_server,handle_msg,5,[{file,"gen_server.erl"},{line,585}]},  
     {proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]},  
     {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]}}}}}} 

我怎么会在这里继续吗?

回答

1

cuttlefish config tool使用可扩展模式。有关于如何在https://github.com/basho/cuttlefish/wiki/Cuttlefish-for-Erlang-Developers

写入新的设置参考下面的块将定义一个riak.conf设置看起来应该像这样的:

erlang.distribution.interface = 192.168.0.42

和翻译功能,把它转换成一个四元组并将其插入到生成的app.config像这样:

{kernel,[{inet_dist_use_interface, {192,168,0,42}}]}

您可以将该块添加到在/ usr /李现有.schema文件B /了Riak/lib中。 或者您可以创建一个新的模式文件,如“0-my-custom.schema”,以使其在升级过程中不太可能被踩踏。

{mapping, "erlang.distribution.interface", "kernel.inet_dist_use_interface", [ 
    {commented, "true"}, 
    {datatype, string}, 
    hidden 
]}. 

{translation, "kernel.inet_dist_use_interface", 
fun(Conf) -> 
    IPStr = cuttlefish:conf_get("erlang.distribution.interface", Conf), 
    list_to_tuple([ list_to_integer(Octet) || Octet <- string:tokens(IPStr,".")]) 
end 
}. 
+0

嗨,乔。太棒了。这确实如此。不知道我可能错过了乌贼图案。非常感谢! –