-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-25568][Core]Continue to update the remaining accumulators when failing to update one accumulator #22586
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
Conversation
|
Test build #96777 has finished for PR 22586 at commit
|
|
Test build #96776 has finished for PR 22586 at commit
|
|
Test build #96778 has finished for PR 22586 at commit
|
|
Test build #96779 has finished for PR 22586 at commit
|
| assert(sc.parallelize(1 to 10, 2).count() === 10) | ||
| } | ||
|
|
||
| test("misbehaved accumulator should not impact other accumulators") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also verify the log message?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also verify the log message?
That's not in the core project.
|
LGTM cc @cloud-fan |
|
This was introduced by AccumulatorV2. It might be a blocker issue for Spark 2.4, since this could return an incorrect result. |
HeartSaVioR
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for this patch, and follow-up issue (SPARK-25569) totally makes sense to me.
…n failing to update one accumulator ## What changes were proposed in this pull request? Since we don't fail a job when `AccumulatorV2.merge` fails, we should try to update the remaining accumulators so that they can still report correct values. ## How was this patch tested? The new unit test. Closes #22586 from zsxwing/SPARK-25568. Authored-by: Shixiong Zhu <[email protected]> Signed-off-by: gatorsmile <[email protected]> (cherry picked from commit b6b8a66) Signed-off-by: gatorsmile <[email protected]>
…n failing to update one accumulator ## What changes were proposed in this pull request? Since we don't fail a job when `AccumulatorV2.merge` fails, we should try to update the remaining accumulators so that they can still report correct values. ## How was this patch tested? The new unit test. Closes #22586 from zsxwing/SPARK-25568. Authored-by: Shixiong Zhu <[email protected]> Signed-off-by: gatorsmile <[email protected]> (cherry picked from commit b6b8a66) Signed-off-by: gatorsmile <[email protected]>
…n failing to update one accumulator ## What changes were proposed in this pull request? Since we don't fail a job when `AccumulatorV2.merge` fails, we should try to update the remaining accumulators so that they can still report correct values. ## How was this patch tested? The new unit test. Closes #22586 from zsxwing/SPARK-25568. Authored-by: Shixiong Zhu <[email protected]> Signed-off-by: gatorsmile <[email protected]> (cherry picked from commit b6b8a66) Signed-off-by: gatorsmile <[email protected]>
|
Thanks! Merged to master/2.4/2.3/2.2 |
…n failing to update one accumulator ## What changes were proposed in this pull request? Since we don't fail a job when `AccumulatorV2.merge` fails, we should try to update the remaining accumulators so that they can still report correct values. ## How was this patch tested? The new unit test. Closes apache#22586 from zsxwing/SPARK-25568. Authored-by: Shixiong Zhu <[email protected]> Signed-off-by: gatorsmile <[email protected]>
…n failing to update one accumulator ## What changes were proposed in this pull request? Since we don't fail a job when `AccumulatorV2.merge` fails, we should try to update the remaining accumulators so that they can still report correct values. ## How was this patch tested? The new unit test. Closes apache#22586 from zsxwing/SPARK-25568. Authored-by: Shixiong Zhu <[email protected]> Signed-off-by: gatorsmile <[email protected]> (cherry picked from commit b6b8a66) Signed-off-by: gatorsmile <[email protected]>
…n failing to update one accumulator ## What changes were proposed in this pull request? Since we don't fail a job when `AccumulatorV2.merge` fails, we should try to update the remaining accumulators so that they can still report correct values. ## How was this patch tested? The new unit test. Closes apache#22586 from zsxwing/SPARK-25568. Authored-by: Shixiong Zhu <[email protected]> Signed-off-by: gatorsmile <[email protected]> (cherry picked from commit b6b8a66) Signed-off-by: gatorsmile <[email protected]>
…n failing to update one accumulator Ref: LIHADOOP-42001 Since we don't fail a job when `AccumulatorV2.merge` fails, we should try to update the remaining accumulators so that they can still report correct values. The new unit test. Closes apache#22586 from zsxwing/SPARK-25568. Authored-by: Shixiong Zhu <[email protected]> Signed-off-by: gatorsmile <[email protected]> (cherry picked from commit b6b8a66) RB=1489248 BUG=LIHADOOP-42001 G=superfriends-reviewers R=fli,mshen,yezhou,edlu A=yezhou
What changes were proposed in this pull request?
Since we don't fail a job when
AccumulatorV2.mergefails, we should try to update the remaining accumulators so that they can still report correct values.How was this patch tested?
The new unit test.