GitHub user KaiXinXiaoLei opened a pull request:
https://github.com/apache/spark/pull/9129
[YARN] When driver sends message "GetExecutorLossReason" to AM, there
should have reture value
I get lastest code form github, and just run "bin/spark-shell --master
yarn --conf spark.dynamicAllocation.enabled=true --conf
spark.dynamicAllocation.initialExecutors=1 --conf
spark.shuffle.service.enabled=true". There is error infor:
15/10/13 10:20:06 ERROR TransportChannelHandler: Connection to /IP:45380
has been quiet for 120000 ms while there are outstanding requests. Assuming
connection is dead; please adjust spark.network.timeout if this is wrong.
15/10/13 10:20:06 ERROR TransportResponseHandler: Still have 1 requests
outstanding when connection from HOSTNAME/IP:45380 is closedclosed.
From log, when driver sends message "GetExecutorLossReason" to AM, the
error appears. From code, i think AM gets this message, should reply.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/KaiXinXiaoLei/spark ExecutorLostReasonReturn
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/9129.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #9129
----
commit ec8d4f7561de1a73ca4195fd0b9883864784f5fd
Author: KaiXinXiaoLei <huleil...@huawei.com>
Date: 2015-10-15T02:28:51Z
there should have reture value
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
