In general today, large amounts of hints still pretty much makes a node angry (just no longer nearly as nasty as it was before), unless you have a really low throughput, you're probably not going to gain much in practice by raising the hints window today.
Later on when we get file system based hints in 3.0 I think your approach will work better, today I'm concerned in practice larger hint windows won't buy you a lot see the following for details. http://www.datastax.com/dev/blog/whats-coming-to-cassandra-in-3-0-improved-hint-storage-and-delivery On Tue, Jan 6, 2015 at 1:47 AM, Jens Rantil <jens.ran...@tink.se> wrote: > Thanks for input, Rob. Just making sure, is "older version" the same as > "less than version 2"? > > > > On Mon, Jan 5, 2015 at 8:13 PM, Robert Coli <rc...@eventbrite.com> wrote: > >> On Mon, Jan 5, 2015 at 2:52 AM, Jens Rantil <jens.ran...@tink.se> wrote: >> >> >>> Since repair is a slow and daunting process*, I am considering >>> increasing max_hint_window_in_ms from its default value of one (1) hour to >>> something like 24-48 hours. >>> ... >>> Are there any other implications of making this change that I haven’t >>> thought of? >>> >> >> Not really, though 24-48 hours of hints could be an awful lot of hints. I >> personally run with at least a 6 hour max_h_w_i_m. >> >> In older versions of Cassandra, 24-48 hours of hints could hose your node >> via ineffective constant compaction. >> >> =Rob >> > > -- Thanks, Ryan Svihla
