Skip to content
This repository has been archived by the owner on May 6, 2021. It is now read-only.

Reduce krakenFailThreshold to 5 minutes (bnc#903007) #93

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tserong
Copy link
Contributor

@tserong tserong commented Apr 10, 2015

This means if the cluster loses quorum, it will take only 5 minutes for
the "cluster updates are stale" warning to appear, rather than 15
minutes (see #75 for
discussion).

Signed-off-by: Tim Serong [email protected]

This means if the cluster loses quorum, it will take only 5 minutes for
the "cluster updates are stale" warning to appear, rather than 15
minutes (see ceph#75 for
discussion).

Signed-off-by: Tim Serong <[email protected]>
@ChristinaMeno
Copy link
Contributor

@tserong over the weekend we discovered an issue http://tracker.ceph.com/issues/11379 that I think should be fixed before reducing the threshold. What do you think?

@tserong
Copy link
Contributor Author

tserong commented Apr 20, 2015

Oh, yuck, browser clock :-/ I could go either way on fixing 11379 first, but you're right, a skewed browser clock will hit the timeout quicker if the threshold is reduced.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants