Thats true.Will re look in to server logs and get back. Br/Akhtar
On Fri, Nov 21, 2014 at 5:09 PM, Mark Reddy <mark.l.re...@gmail.com> wrote: > I believe you were attempting to share: > https://issues.apache.org/jira/browse/CASSANDRA-8352 > > Your cassandra logs outputs the following: > >> DEBUG [Thrift:4] 2014-11-20 15:36:50,653 CustomTThreadPoolServer.java >> (line 204) Thrift transport error occurred during processing of message. >> org.apache.thrift.transport.TTransportException: Cannot read. Remote side >> has closed. Tried to read 4 bytes, but only got 0 bytes. (This is often >> indicative of an internal error on the server side. Please check your >> server logs.) > > > Which indicates that your server is under pressure at that moment and > points you to look at your server logs for further diagnosis. > > > Mark > > On 21 November 2014 11:15, Akhtar Hussain (JIRA) <j...@apache.org> wrote: > >> Akhtar Hussain shared a search result with you >> ----------------------------- >> >> >> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=reporter+%3D+currentUser%28%29+ORDER+BY+createdDate+DESC >> >> We have a Geo-red setup with 2 Data centers having 3 nodes each. When >> we bring down a single Cassandra node down in DC2 by kill -9 >> <Cassandra-pid>, reads fail on DC1 with TimedOutException for a brief >> amount of time (15-20 sec~). >> >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.3.4#6332) >> > >
