Yes.. .it's not currently possible :) I think it should be.
Say the IO on your C* is at 60% utilization. If you do a repair, this would require 120% utilization obviously not possible, so now your app is down / offline until the repair finishes. If you could throttle repair separately this would resolve this problem. IF anyone else thinks this is an issue I'll create a JIRA. On Mon, Oct 19, 2015 at 3:38 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Mon, Oct 19, 2015 at 9:30 AM, Kevin Burton <bur...@spinn3r.com> wrote: > >> I think the point I was trying to make is that on highly loaded boxes, >> repair should take lower priority than normal compactions. >> > > You can manually do this by changing the thread priority of compaction > threads which you somhow identify as doing repair related compaction... > > ... but incoming streamed SStables are compacted just as if they were > flushed, so I'm pretty sure what you're asking for is not currently > possible? > > =Rob > > -- We’re hiring if you know of any awesome Java Devops or Linux Operations Engineers! 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>
