Socket closed during write?
brad at cloudability.com
Thu Jan 10 12:58:55 EST 2013
All nodes, but one at a time. It seems to be whichever one is servicing the request.
On Jan 10, 2013, at 9:57 AM, Evan Vigil-McClanahan <emcclanahan at basho.com> wrote:
> Does this happen on all of the nodes, or just one? One client, or all
> of them? A particular type of request, or just at random?
> On Thu, Jan 10, 2013 at 1:29 AM, Brad Heller <brad at cloudability.com> wrote:
>> I'm using regular ol' ruby-riak client to write to the bucket. It's all pretty much out of the box. There is an ELB in front of the ring with SSL on the ELB and on passed through to the ring, if that's significant.
>> Nothing special that I can identify. I can attempt to instrument our code further...
>> On Jan 9, 2013, at 10:05 PM, Evan Vigil-McClanahan <emcclanahan at basho.com> wrote:
>>> The last time I saw this particular error it was someone on a 64bit
>>> client setting the content length value incorrectly via libcurl.
>>> Requests would work on 64 bit nodes but fail on 32 bit nodes,
>>> presumably because the HTTP client was handing the socket a garbage
>>> value to read, thereby killing it.
>>> Timeouts will generally return a different error. You might be
>>> looking at some TCP or HTTP issue. How are you connecting? Is there
>>> anything special about the requests that are failing?
>>> On Wed, Jan 9, 2013 at 7:29 PM, Brad Heller <brad at cloudability.com> wrote:
>>>> Hey all,
>>>> I've got a mysterious error with Riak. Certain writes seem to result in an
>>>> interesting error being raised by the coordinating node (rem, I'm assuming
>>>> it's the coordinating node):
>>>> webmachine error: path="/buckets/my_bucket/keys"
>>>> Web machine returns a 500 error when this happens. I saw online that this
>>>> could be the result of a socket being closed out from under the connection
>>>> . Any idea how I can get to the bottom of this? Due to the nature of the
>>>> reproduction steps, I don't have access to the payload causing the crash
>>>> 'till it's actually *in* Riak. Someone in #riak on IRC suggested that this
>>>> could be the result of write timeouts. Ideas?
>>>> Brad Heller
>>>> riak-users mailing list
>>>> riak-users at lists.basho.com
More information about the riak-users