-
Notifications
You must be signed in to change notification settings - Fork 183
Closed
Labels
Description
Very occasionally, I'll see a RiakError (with no further details) raised during the execution of my code, typically when calling the store() method on a riak object (with no arguments).
The traceback (starting from the line immediately after the store() call) looks like this:
File "/home/ubuntu/env/local/lib/python2.7/site-packages/riak/riak_object.py", line 286, in store
timeout=timeout)
File "/home/ubuntu/env/local/lib/python2.7/site-packages/riak/client/transport.py", line 196, in wrapper
return self._with_retries(pool, thunk)
File "/home/ubuntu/env/local/lib/python2.7/site-packages/riak/client/transport.py", line 138, in _with_retries
return fn(transport)
File "/home/ubuntu/env/local/lib/python2.7/site-packages/riak/client/transport.py", line 194, in thunk
return fn(self, transport, *args, **kwargs)
File "/home/ubuntu/env/local/lib/python2.7/site-packages/riak/client/operations.py", line 554, in put
timeout=timeout)
File "/home/ubuntu/env/local/lib/python2.7/site-packages/riak/transports/pbc/transport.py", line 220, in put
MSG_CODE_PUT_RESP)
File "/home/ubuntu/env/local/lib/python2.7/site-packages/riak/transports/pbc/connection.py", line 56, in _request
return self._recv_msg(expect)
File "/home/ubuntu/env/local/lib/python2.7/site-packages/riak/transports/pbc/connection.py", line 178, in _recv_msg
raise RiakError(bytes_to_str(err.errmsg))
RiakErrorIt happens very rarely, and I haven't been able to reproduce it on demand yet to uncover the actual problem. In the meantime, I would appreciate any suggestions on the best way to handle this. Should I catch the RiakError in the application level, wrapping the .store() call in a try/catch block? Or is there a better way?
Thanks in advance.
Reactions are currently unavailable