[jira] [Commented] (HIVE-15887) could not get APP ID and cause failed to connect to spark driver on yarn-client mode

2017-02-14 Thread Rui Li (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867150#comment-15867150 ] Rui Li commented on HIVE-15887: --- The symptom is quite similar to that of HIVE-12650. Is this a busy cluster?

[jira] [Commented] (HIVE-15887) could not get APP ID and cause failed to connect to spark driver on yarn-client mode

2017-02-14 Thread KaiXu (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865627#comment-15865627 ] KaiXu commented on HIVE-15887: -- it seems like that, Hive side timeout after hive.spark.job.monitor.timeout,

[jira] [Commented] (HIVE-15887) could not get APP ID and cause failed to connect to spark driver on yarn-client mode

2017-02-14 Thread Rui Li (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865384#comment-15865384 ] Rui Li commented on HIVE-15887: --- In the AM log, the "failure to connect to driver" happened around 5:05.

[jira] [Commented] (HIVE-15887) could not get APP ID and cause failed to connect to spark driver on yarn-client mode

2017-02-13 Thread KaiXu (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864894#comment-15864894 ] KaiXu commented on HIVE-15887: -- this issue occurred again yesterday, to be notable, this issue occurred when

[jira] [Commented] (HIVE-15887) could not get APP ID and cause failed to connect to spark driver on yarn-client mode

2017-02-13 Thread KaiXu (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864877#comment-15864877 ] KaiXu commented on HIVE-15887: -- >From nodemanager log, can only see container transitioned from LOCALIZED to

[jira] [Commented] (HIVE-15887) could not get APP ID and cause failed to connect to spark driver on yarn-client mode

2017-02-13 Thread KaiXu (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864837#comment-15864837 ] KaiXu commented on HIVE-15887: -- Hi [~lirui], above container log is the yarn application log, the middle has

[jira] [Commented] (HIVE-15887) could not get APP ID and cause failed to connect to spark driver on yarn-client mode

2017-02-13 Thread Rui Li (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863645#comment-15863645 ] Rui Li commented on HIVE-15887: --- Seems the application is ACCEPTED but didn't reach RUNNING. YARN log may be

[jira] [Commented] (HIVE-15887) could not get APP ID and cause failed to connect to spark driver on yarn-client mode

2017-02-13 Thread KaiXu (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863605#comment-15863605 ] KaiXu commented on HIVE-15887: -- Thanks Rui Li for the information, the JIRA was first loged on Spark by

[jira] [Commented] (HIVE-15887) could not get APP ID and cause failed to connect to spark driver on yarn-client mode

2017-02-13 Thread Rui Li (JIRA)
[ https://issues.apache.org/jira/browse/HIVE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863160#comment-15863160 ] Rui Li commented on HIVE-15887: --- Hi [~KaiXu], the failure is just a warning and it shouldn't make the query