As a side note, be aware that running with DEBUG logging enabled can make your cluster run a full order of magnitude slower.
On Mon, May 9, 2011 at 6:54 PM, Suan Aik Yeo <yeosuan...@gmail.com> wrote: > Ah, must be the status check that I set up. Thanks! > > > On Mon, May 9, 2011 at 7:42 PM, Tyler Hobbs <ty...@datastax.com> wrote: > >> It just means a client connection was closed. >> >> >> On Mon, May 9, 2011 at 5:41 PM, Suan Aik Yeo <yeosuan...@gmail.com>wrote: >> >>> I have a Cassandra 0.7.0, 3 node cluster with logging set to DEBUG. A few >>> days ago, and I'm not sure what triggered this, the logs started showing >>> messages like >>> DEBUG 17:37:30,399 logged out: #<User allow_all groups=[]> >>> every second or so, regardless whether there was Cassandra activity. >>> Today I just upgraded to 0.7.5, and they're still there. Apart from blowing >>> up the log file sizes, what do these messages mean? >>> >>> Thanks, >>> Suan >>> >> >> >> >> -- >> Tyler Hobbs >> Software Engineer, DataStax <http://datastax.com/> >> Maintainer of the pycassa <http://github.com/pycassa/pycassa> Cassandra >> Python client library >> >> >
