Hi Jon,
Yes, your jdm-msglen-fix tree seems to resolve the issue for me;
however, I'm only currently using (and likewise only testing) .store()
operations with the python client. With the un-patched version, the
issue occurred for me every time I tried to store data -- of course, my
data is p
Hi Bob/Nico/Gary
Thanks for submitting the pull request. I took a look at the patch and
would prefer to keep the packet length check in, but just move it to the
right place.
I'm unable to reproduce the issue locally, but wondered if you'd be able to
try out the
https://github.com/basho/riak-pyt
Thanks, Nico. I forked riak-python-client and created a pull request for
the patch you described (removing the three lines for the length check
in recv _pkt).
- Bob Feldbauer
On 1/22/2011 3:23 AM, Nico Meyer wrote:
Hi
let me clarify the situation somewhat. The problem is not intermittent
in
Hi,
let me clarify the situation somewhat. The problem is not intermittent
in the sense that it occurs randomly. It depends mainly on the size of
the answer that riak sends. If the answer is bigger than the network MTU
the error will occur most of the time. If its smaller it occurs almost
never. T
I had the same problem the other day and someone answered with the
fix. So search the archives on my name to find the precise answer.
But the fix was to remove the three lines in pbc.py where the check
and error message occur. Basically this is a known issue and the
check should not be there.
-
It looks like other people are experiencing this issue too
https://issues.basho.com/show_bug.cgi?id=695
Looking at recv_pkt the checks for short read should be outside of that
while loop, as it's perfectly valid to return shorter reads due to signals.
For now it's probably safe to comment it out
Interesting. I was actually seeing this all the time, not just
intermittently. Removing the lines as described in bug #695
(https://issues.basho.com/show_bug.cgi?id=695) did resolve my issue.
Thanks for the help, Gary.
- Bob
On 1/21/2011 2:28 PM, Gary Flake wrote:
I had the same problem the
Hi Bob,
That sounds like a tricky one. Does it depend on the data you already have
in Riak? Can you reproduce with a small script that runs against an empty
node? If so send it over and I'll take a look.
Jon
On Fri, Jan 21, 2011 at 2:48 PM, Bob Feldbauer wrote:
> Thanks for the suggestion, Jo
Thanks for the suggestion, Jon. This is occurring every time I try to do
.store() via protobuf transport in the Python client (so yes, it is
reproducible); however, there is no output in logs or riak console.
- Bob
On 1/21/2011 1:02 PM, Jon Meredith wrote:
Hi Bob,
That sounds like the connec
Hi Bob,
That sounds like the connection got closed as the client was readying.
Have you checked through the server logs to verify that no processes died or
no other nodes went down? Or if it's reproducible you should be able to
start the server with 'riak console' and see what gets printed.
Che
10 matches
Mail list logo
