cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: tcp CLOSE_WAIT bug
Date Mon, 19 Apr 2010 20:47:03 GMT
Is this after doing a bootstrap or other streaming operation?  Or did
a node go down?

The internal sockets are supposed to remain open, otherwise.

On Mon, Apr 19, 2010 at 10:56 AM, Ingram Chen <ingramchen@gmail.com> wrote:
> Thank your information.
>
> We do use connection pools with thrift client and ThriftAdress is on port
> 9160.
>
> Those problematic connections we found are all in port 7000, which is
> internal communications port between
> nodes. I guess this related to StreamingService.
>
> On Mon, Apr 19, 2010 at 23:46, Brandon Williams <driftx@gmail.com> wrote:
>>
>> On Mon, Apr 19, 2010 at 10:27 AM, Ingram Chen <ingramchen@gmail.com>
>> wrote:
>>>
>>> Hi all,
>>>
>>>     We have observed several connections between nodes in CLOSE_WAIT
>>> after several hours of operation:
>>
>> This is symptomatic of not pooling your client connections correctly.  Be
>> sure you're using one connection per thread, not one connection per
>> operation.
>> -Brandon
>
>
> --
> Ingram Chen
> online share order: http://dinbendon.net
> blog: http://www.javaworld.com.tw/roller/page/ingramchen
>

Mime
View raw message