Ok. For the mixed cluster case where the module may not be available/in basho-patches what do you think? 

It seems like we can guard it by a capability since it will always first be executed on a Riak node  

Not sure about the requirements of having that done for merge though given the state of mixed clusters right now...

Sent from my iPhone

> On Dec 22, 2013, at 4:41 AM, Scott Lystig Fritchie <notifications@github.com> wrote:
> 
> In src/riak_core_util.erl:
> 
> > @@ -581,6 +583,100 @@ make_fold_reqv(v2, FoldFun, Acc0, Forwardable, Opts)
> >      ?FOLD_REQ{foldfun=FoldFun, acc0=Acc0,
> >                forwardable=Forwardable, opts=Opts}.
> >  
> > +-define(REGNAME, net_kernel_net_ticktime_change_daemon).
> > +
> > +start_set_net_ticktime_daemon(Node, Time) ->
> > +    EbinDir = filename:dirname(code:which(?MODULE)),
> > +    try
> > +        Dirs = rpc:call(Node, code, get_path, []),
> > +        case lists:member(EbinDir, Dirs) of
> > +            false ->
> > +                lager:info("start_set_net_ticktime_daemon: adding to code path "
> > +                           "for node ~p\n", [Node]),
> > +                rpc:call(Node, code, add_pathz, [EbinDir]);
> Yes, I've noticed that too, but it doesn't happen in the common case when the Riak nodes are on separate machines.
> 
> AFAIK, nodetool isn't talking other other nodes in this case.
> 
> —
> Reply to this email directly or view it on GitHub.