Thank you for your reply, Tomita. So the node may have failed to response in time, but other nodes might have completed it's request. (in QUORUM) This helps my mind that it's not a definite failure. ;-)
However, I do not understand what you meant to check data. Checking data of dropped request... is not easy, since I do not know which request was dropped. Are there some options to turn on? Best wishes On 11/18/11, K.Tomita <tomitakazut...@intheforest.jp> wrote: > Hello, Jeesoo. > > I was investigating it exactly. > > It means,when RPC service does not return a status > for a defined period of time, > the value is incremented. > (cassandra.yaml:rpc_timeout_in_ms) > (default:10000) > > Therefore, > The Drop is assumed that, > there is a possibility that distribution node is completed processing, > and there is a possibility of having failed. > > So, I recommend checking the data on a distribution node. > > > ** I hope tomorrow will be a good day ** > > Tomita Kazutaka > > mailto : tomitakazut...@intheforest.jp > blog : http://www.intheforest.jp/blog/ > twitter: http://twitter.com/railute > ***** **** **** **** **** **** **** **** > > > > 2011/11/17 Jeesoo Shin <bsh...@gmail.com>: >> Hello. >> I'm using cassandra 0.8.6 >> with nodetool tpstats, dropped statistics are shown. >> >> when drop happens... what can I do? >> are there ways to turn on debug messages or to look into? >> >> thanks. >> >
