ITC threads are started as soon as the other party connects. On Tue, Sep 27, 2011 at 9:22 PM, Yang <teddyyyy...@gmail.com> wrote: > found the reason. > > the IncomingTCPConnection.run() hit an exception and the thread > terminated. the next incarnation of the thread did not come up until > 20 seconds later, which caused the TimedOutException and > UNavalableException to clients. > > > > WARN [Thread-28] 2011-09-28 02:17:57,561 IncomingTcpConnection.java > (line 122) eof reading from socket; closing > java.io.EOFException > at java.io.DataInputStream.readInt(DataInputStream.java:392) > at > org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:112) > > > > I don't know whether the EOF here is really due to network or something in > code > (if it's really network, is there a way to let IncomingTCPConnection > fire up the next one faster? like within 1 second.... I'm reading > through the code to find it ) > > Thanks > Yang > > > > On Sun, Sep 25, 2011 at 1:04 PM, Brandon Williams <dri...@gmail.com> wrote: >> On Sun, Sep 25, 2011 at 1:10 PM, Yang <teddyyyy...@gmail.com> wrote: >>> Thanks Brandon. >>> >>> I'll try this. >>> >>> but you can also see my later post regarding message drop : >>> http://mail-archives.apache.org/mod_mbox/cassandra-user/201109.mbox/%3ccaanh3_8aehidyh9ybt82_emh3likbcdsenrak3jhfzaj2l+...@mail.gmail.com%3E >>> >>> that seems to show something in either code or background load causing >>> messages to be really dropped >> >> I see. My guess is then this: there is a local clock problem, causing >> generations to be the same, thus not notifying the FD. So perhaps the >> problem is not network-related, but it is something in the ec2 >> environment. >> >> -Brandon >> >
-- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
