This repository was archived by the owner on Oct 11, 2025. It is now read-only.
Log the exception why we're aborting the whole mapreduce #111
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
My multiple-day-long mapreduce just died. Without any retries. Without any log statements explaining why. Sigh. I'm not going to push for a retry (since arguably the preprocess would just repeatedly fail, and one can agree/disagree as to whether it should retry with the intent that the programmer fixes something on a subsequent retry). But it should at the very least log the exception, so the programmer can attempt to fix it, before he or she attempts to run the multiple-day-long mapreduce again.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My multiple-day-long mapreduce just died. Without any retries. Without any log statements explaining why. Sigh.
I'm not going to push for a retry (since arguably the preprocess would just repeatedly fail, and one can agree/disagree as to whether it should retry with the intent that the programmer fixes something on a subsequent retry).
But it should at the very least log the exception, so the programmer can attempt to fix it, before he or she attempts to run the multiple-day-long mapreduce again.