Thanks. Depending on the whole infrastructure and business requirements, isn't it easier to implement throttling at the client side? I did this once to throttle bulk inserts to migrate whole CFs from other DBs.
2017-02-21 7:43 GMT+01:00 Jeff Jirsa <jji...@apache.org>: > > > On 2017-02-20 21:35 (-0800), Benjamin Roth <benjamin.r...@jaumo.com> > wrote: > > Stupid question: > > Why do you rate limit a database, especially writes. Wouldn't that cause > a > > lot of new issues like back pressure on the rest of your system or > timeouts > > in case of blocking requests? > > Also rate limiting has to be based on per coordinator calculations and > not > > cluster wide. It reminds me on hinted handoff throttling. > > > > If you're sharing one cluster with 10 (or 20, or 100) applications, > breaking one application may be better than slowing down 10/20/100. In many > cases, workloads can be throttled and still meet business goals - nightly > analytics jobs, for example, may be fine running over the course of 3 hours > instead of 15 minutes, especially if the slightly-higher-response-latency > over 3 hours is better than much-worse-response-latency for that 15 minute > window. > -- Benjamin Roth Prokurist Jaumo GmbH · www.jaumo.com Wehrstraße 46 · 73035 Göppingen · Germany Phone +49 7161 304880-6 · Fax +49 7161 304880-1 AG Ulm · HRB 731058 · Managing Director: Jens Kammerer
