I suspect there may be a connection between "the server was busy with something and didn't die immediately with kill -INT" and "I was getting timeout exceptions."
On Tue, Nov 10, 2009 at 2:42 PM, Chris Were <chris.w...@gmail.com> wrote: > As in... kill -9 > > On Tue, Nov 10, 2009 at 12:38 PM, Jonathan Ellis <jbel...@gmail.com> wrote: >> >> it's supposed to be kill-only. curious what shutdown you were trying. >> >> On Tue, Nov 10, 2009 at 2:19 PM, Chris Were <chris.w...@gmail.com> wrote: >> > I've restarted with debugging and it seems to be ok for the time being. >> > Interesting to note that cassandra wouldn't shut down properly and had >> > to be >> > killed. >> > >> > On Tue, Nov 10, 2009 at 11:55 AM, Jonathan Ellis <jbel...@gmail.com> >> > wrote: >> >> >> >> if you're timing out doing a slice on 10 columns w/ 10% cpu used, >> >> something is broken >> >> >> >> is it consistent as to which keys this happens on? try turning on >> >> debug logging and seeing where the latency is coming from. >> >> >> >> On Tue, Nov 10, 2009 at 1:53 PM, Chris Were <chris.w...@gmail.com> >> >> wrote: >> >> > >> >> > On Tue, Nov 10, 2009 at 11:50 AM, Jonathan Ellis <jbel...@gmail.com> >> >> > wrote: >> >> >> >> >> >> On Tue, Nov 10, 2009 at 1:49 PM, Chris Were <chris.w...@gmail.com> >> >> >> wrote: >> >> >> > Maybe... but it's not just multigets, it also happens when >> >> >> > retreiving >> >> >> > one >> >> >> > row with get_slice. >> >> >> >> >> >> how many of the 3M columns are you trying to slice at once? >> >> > >> >> > Sorry, I must have mixed up the terminology. >> >> > There's ~3M keys, but less than 10 columns in each. The get_slice >> >> > calls >> >> > are >> >> > to retreive all the columns (10) for a given key. >> > >> > > >
