You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "TheWindIsRising (via GitHub)" <gi...@apache.org> on 2023/02/13 05:56:28 UTC

[GitHub] [dolphinscheduler] TheWindIsRising opened a new issue, #13556: ERROR yarn.Client: Application diagnostics message: Max number of executor failures (4) reached

TheWindIsRising opened a new issue, #13556:
URL: https://github.com/apache/dolphinscheduler/issues/13556

   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
   
   
   ### What happened
   
   K8s deploys ds and uses the external hdp cluster for task scheduling error information
   23/02/13 11:31:34 ERROR yarn.Client: Application diagnostics message: Max number of executor failures (4) reached
   	Exception in thread "main" org.apache.spark.SparkException: Application application_1675841615889_0042 finished with failed status
   		at org.apache.spark.deploy.yarn.Client.run(Client.scala:1150)
   		at org.apache.spark.deploy.yarn.YarnClusterApplication.start(Client.scala:1530)
   		at org.apache.spark.deploy.SparkSubmit.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:845)
   		at org.apache.spark.deploy.SparkSubmit.doRunMain$1(SparkSubmit.scala:161)
   		at org.apache.spark.deploy.SparkSubmit.submit(SparkSubmit.scala:184)
   		at org.apache.spark.deploy.SparkSubmit.doSubmit(SparkSubmit.scala:86)
   		at org.apache.spark.deploy.SparkSubmit$$anon$2.doSubmit(SparkSubmit.scala:920)
   		at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:929)
   		at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
   	23/02/13 11:31:34 INFO util.ShutdownHookManager: Shutdown hook called
   
   ### What you expected to happen
   
   K8s deploys ds and uses the external hdp cluster for task scheduling error information
   
   ### How to reproduce
   
   23/02/13 11:31:34 ERROR yarn.Client: Application diagnostics message: Max number of executor failures (4) reached
   	Exception in thread "main" org.apache.spark.SparkException: Application application_1675841615889_0042 finished with failed status
   		at org.apache.spark.deploy.yarn.Client.run(Client.scala:1150)
   		at org.apache.spark.deploy.yarn.YarnClusterApplication.start(Client.scala:1530)
   		at org.apache.spark.deploy.SparkSubmit.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:845)
   		at org.apache.spark.deploy.SparkSubmit.doRunMain$1(SparkSubmit.scala:161)
   		at org.apache.spark.deploy.SparkSubmit.submit(SparkSubmit.scala:184)
   		at org.apache.spark.deploy.SparkSubmit.doSubmit(SparkSubmit.scala:86)
   		at org.apache.spark.deploy.SparkSubmit$$anon$2.doSubmit(SparkSubmit.scala:920)
   		at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:929)
   		at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
   	23/02/13 11:31:34 INFO util.ShutdownHookManager: Shutdown hook called
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.1.x
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #13556: ERROR yarn.Client: Application diagnostics message: Max number of executor failures (4) reached

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #13556:
URL: https://github.com/apache/dolphinscheduler/issues/13556#issuecomment-1427389150

   Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
   * In order for us to understand your request as soon as possible, please provide detailed information, version or pictures.
   * If you haven't received a reply for a long time, you can [join our slack](https://s.apache.org/dolphinscheduler-slack) and send your question to channel `#troubleshooting`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [dolphinscheduler] SbloodyS commented on issue #13556: ERROR yarn.Client: Application diagnostics message: Max number of executor failures (4) reached

Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS commented on issue #13556:
URL: https://github.com/apache/dolphinscheduler/issues/13556#issuecomment-1427511574

   It looks like a spark issue. Please send it to the spark community.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [dolphinscheduler] SbloodyS closed issue #13556: ERROR yarn.Client: Application diagnostics message: Max number of executor failures (4) reached

Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS closed issue #13556: ERROR yarn.Client: Application diagnostics message: Max number of executor failures (4) reached
URL: https://github.com/apache/dolphinscheduler/issues/13556


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org