eems to loop forever...
> after both Cassandra instances were restarted the problem didn't occur.
>
> Best regards, Daniel.
>
--
Ingram Chen
online share order: http://dinbendon.net
blog: http://www.javaworld.com.tw/roller/page/ingramchen
t supposed to ever terminate unless a node
> dies or is partitioned. So if we "fix" it by adding a socket.close I
> worry that we're covering up something more important.
>
> On Wed, Apr 21, 2010 at 8:53 PM, Ingram Chen wrote:
> > I agree your point. I patch th
Ellis wrote:
> I'd like to get something besides "I'm seeing close wait but i have no
> idea why" for a bug report, since most people aren't seeing that.
>
> On Tue, Apr 20, 2010 at 9:33 AM, Ingram Chen wrote:
> > I trace IncomingStreamReader source
I trace IncomingStreamReader source and found that incoming socket comes
from MessagingService$SocketThread.
but there is no close() call on either accepted socket or socketChannel.
Should I file a bug report ?
On Tue, Apr 20, 2010 at 11:02, Ingram Chen wrote:
> this happened after seve
th logs for exceptions?
>
> On Mon, Apr 19, 2010 at 9:36 PM, Ingram Chen wrote:
> > Ouch ! I talk too early !
> >
> > We still suffer same problems after upgrade to 1.6.0_20.
> >
> > In JMX StreamingService, I see several wired incoming/outgoing transfer:
>
trap 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
> wrote:
> > Thank your information.
> >
> > We do use connection pools with t
ead += fc.transferFrom(socketChannel, bytesRead,
FileStreamTask.CHUNK_SIZE);
pendingFile.update(bytesRead);
}
On Tue, Apr 20, 2010 at 05:48, Rob Coli wrote:
> On 4/17/10 6:47 PM, Ingram Chen wrote:
>
>> after upgrading jdk from 1.6.0_16 to 1.6.0_20, the problem solved.
>>
, Brandon Williams wrote:
> On Mon, Apr 19, 2010 at 10:27 AM, Ingram Chen 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 clien
Hi all,
We have observed several connections between nodes in CLOSE_WAIT after
several hours of operation:
At node 87:
netstat -tn | grep 7000
tcp0 0 :::192.168.2.87:7000:::192.168.2.88:57625
CLOSE_WAIT
tcp0 0 :::192.168.2.87:7000:::192.168.2
FYI.
after upgrading jdk from 1.6.0_16 to 1.6.0_20, the problem solved.
On Fri, Apr 16, 2010 at 00:33, Ingram Chen wrote:
> Hi all,
>
> We setup two nodes and simply set replication factor=2 for test run.
>
> After both nodes, say, node A and node B, serve several hours,
-b01, mixed mode)
Cassandra --- 0.6.0
Node configuration --- node A and node B. both nodes use node A as Seed
client --- Java thrift clients pick one node randomly to do read and write.
--
Ingram Chen
online share order: http://dinbendon.net
blog: http://www.javaworld.com.tw/roller/page/ingramchen
11 matches
Mail list logo
