It could be a large number of things, unfortunately. To go through them all it somewhat outside of my skill set. Maybe someone more network savvy can provide some pointers?
Perhaps checking with your network admin, or turning any software firewalls on your nodes completely off, as a test? On Thu, Mar 21, 2013 at 11:44 AM, Godefroy de Compreignac <[email protected]> wrote: > But I don't understand what could stop transfers. Maybe a kernel setting? > How could I find out? > > -- > Godefroy de Compreignac > > Eklaweb CEO - www.eklaweb.com > EklaBlog CEO - www.eklablog.com > > +33(0)6 11 89 13 84 > http://www.linkedin.com/in/godefroy > http://twitter.com/Godefroy > > > 2013/3/21 Evan Vigil-McClanahan <[email protected]> >> >> Handoff is done by default on port 8099. >> >> I guess what I am getting at here is that this doesn't look like an >> obvious riak problem, it's more likely that something on your network >> or on your nodes is closing or interrupting those sockets; you'd most >> likely get a different error if something internal to riak was causing >> the transfers to fail. >> >> On Thu, Mar 21, 2013 at 10:09 AM, Godefroy de Compreignac >> <[email protected]> wrote: >> > The only limitation that I'd see is Haproy which have a time limit: >> > contimeout 5000 >> > clitimeout 50000 >> > srvtimeout 3600000 >> > >> > But Haproxy serves Riak on port 8098 and I configured Riak to use port >> > 8097: >> > {pb_port, 8087 } >> > {http, [ {"5.39.68.152", 8097 } ]} >> > >> > So I guess Riak use only port 8097 internally, without any limitation. >> > >> > And by checking logs, I see that a vnode transfer fails after a random >> > duration, sometimes a few minutes. > > _______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
