HI Jeremy,
For more insight into the hint system, these two blog posts are great
resources: http://www.datastax.com/dev/blog/modern-hinted-handoff, and
http://www.datastax.com/dev/blog/whats-coming-to-cassandra-in-3-0-improved-hint-storage-and-delivery
.
For timeframes, that's going to differ bas
hi Bryan,
I guess I want to find out if there is any way to tell when data will
become consistent again in both cases.
if the node being down shorter than the max_hint_window(say 2 hours out of
3 hrs max), is there anyway to check the log or JMX etc to see if the hint
queue size back to zero or lo
Hi Jimmy,
If you sustain a long downtime, repair is almost always the way to go.
It seems like you're asking to what extent a cluster is able to
recover/resync a downed peer.
A peer will not attempt to reacquire all the data it has missed while being
down. Recovery happens in a few ways:
1) Hin
so far they are not long, just some config change and restart.
if it is a 2 hrs downtime due to whatever reason, a repair is better option
than trying to figure out if replication syn finish or not?
On Thu, Feb 25, 2016 at 1:09 PM, daemeon reiydelle
wrote:
> Hmm. What are your processes when a n
Hmm. What are your processes when a node comes back after "a long offline"?
Long enough to take the node offline and do a repair? Run the risk of
serving stale data? Parallel repairs? ???
So, what sort of time frames are "a long time"?
*...*
*Daemeon C.M. ReiydelleUSA (+1) 415.501.0198Lon
hi all,
what are the better ways to check replication overall status of cassandra
cluster?
within a single DC, unless a node is down for long time, most of the time i
feel it is pretty much non-issue and things are replicated pretty fast. But
when a node come back from a long offline, is there