Github user caneGuy commented on the issue:
https://github.com/apache/spark/pull/19399
All right, thanks for the comments and i agree with you.I will close this
one. @jerryshao @ajbozarth @vanzin And try other solutions.
---
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/19399
I'm actually more concerned about the SHS having its own idea of what
success and failure means; it sounds like a source for headaches (why is the
app failed in the SHS but successful in YARN?).
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/19399
With @jerryshao comments I'm going to get off the fence firmly against
this, we already have too many things slowing down the SHS as it is
---
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/19399
I agree with @squito that the criteria to define application's success
should be well considered. Here in your current code, only if all the jobs are
successful then the application is marked as
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/19399
Nice, I think it should be merged.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user caneGuy commented on the issue:
https://github.com/apache/spark/pull/19399
Ok i will wait for SPARK-18085 and think about log status more accurately
@squito @ajbozarth Thanks.
---
-
To unsubscribe,
Github user caneGuy commented on the issue:
https://github.com/apache/spark/pull/19399
@jerryshao @squito Could you help review this?Thanks
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19399
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
