Dietrich -
I haven't seen this in testing or have had anyone report this; could I
get some more info?
What operations are timing out like this? Is that the complete message
in the riak error.log? Which version of Riak are you running?
Do you see this simply dropping in the 1.0.6 client to your existing
application, or is this after changing your code to use the new
'withoutFetch()' ?
Thanks,
Brian Roach
On Wed, Dec 26, 2012 at 7:28 PM, Dietrich Featherston <d...@d2fn.com> wrote:
> I had rolled out an upgrade to a JVM app that uses rjc 1.0.5. We had
> upgraded to 1.0.6 to take advantage of newly added abilities to do a
> put without preceding it with a fetch in order to reduce operational
> load on the cluster. However, after rolling out this change we
> frequently see large rises in latency across the cluster (up to the
> gen_fsm limit of 60s) and see the following in the riak logs
>
> [error] Unrecognized message {74392380,{error,timeout}}
>
> This is accompanied by repeated socket timeouts as seen by the
> riak-java-client.
>
> Also worth mentioning, one of our nodes got into a state that the rjc
> was unable to establish a tcp connection on the protobuf port to riak
> on localhost. We were only able to fix this by restarting the riak
> process on that node and inducing a fair amount of handoff.
>
> Any thoughts?
>
> Thanks,
> D
>
> _______________________________________________
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
