A couple options: 1. You could use nodetool settraceprobability. If lots are slow, you can then go to the system_events.sessions and pick out some slow ones.
2. You could update the metadata (temporarily) on your table and use tracing ad-hoc using cqlsh. Using #1 if you need to pick out exact queries will be incredibly painful unless your cluster is silent. On Sun, Jun 29, 2014 at 7:41 PM, Kevin Burton <bur...@spinn3r.com> wrote: > Is it possible to trace thrift queries? > > We're using KairosDB and *most* of the queries are amazingly slow… even > repeated queries which should be in cache. > > Tracing them should help iron down whats happening. > > Kevin > > -- > > Founder/CEO Spinn3r.com > Location: *San Francisco, CA* > blog: http://burtonator.wordpress.com > … or check out my Google+ profile > <https://plus.google.com/102718274791889610666/posts> > <http://spinn3r.com> > > -- *Ken Hancock *| System Architect, Advanced Advertising SeaChange International 50 Nagog Park Acton, Massachusetts 01720 ken.hanc...@schange.com | www.schange.com | NASDAQ:SEAC <http://www.schange.com/en-US/Company/InvestorRelations.aspx> Office: +1 (978) 889-3329 | [image: Google Talk:] ken.hanc...@schange.com | [image: Skype:]hancockks | [image: Yahoo IM:]hancockks [image: LinkedIn] <http://www.linkedin.com/in/kenhancock> [image: SeaChange International] <http://www.schange.com/>This e-mail and any attachments may contain information which is SeaChange International confidential. The information enclosed is intended only for the addressees herein and may not be copied or forwarded without permission from SeaChange International.
