Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AR-3229 once you hit 500+ indexes or have exceptionally large indexes… #26

Merged
merged 2 commits into from
Feb 22, 2016

Conversation

drewdahlke
Copy link
Contributor

…, the 30s default snapshot timeout in elasticsearch might not be enough. Robustifying to allow up to 30min for snapshot operations.

…, the 30s default snapshot timeout in elasticsearch might not be enough. Robustifying to allow up to 30min for snapshot operations.
}
try {
if(reporter != null) {
reporter.incrCounter(BaseESReducer.JOB_COUNTER.TIMES_BLOCKED_WAITING_FOR_SNAPSHOT, 1);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion. Maybe the time spent waiting would be a better metric? Right now, the amount of time I'm sleeping each cycle dictates what this counter really means.

@gdasbach
Copy link
Contributor

Looks good to me

drewdahlke added a commit that referenced this pull request Feb 22, 2016
AR-3229 once you hit 500+ indexes or have exceptionally large indexes…
@drewdahlke drewdahlke merged commit 024470b into master Feb 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants