You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2018/09/05 18:53:00 UTC
[jira] [Updated] (HIVE-20506) HOS times out when cluster is full
while Hive-on-MR waits
[ https://issues.apache.org/jira/browse/HIVE-20506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brock Noland updated HIVE-20506:
--------------------------------
Description:
My understanding is as follows:
Hive-on-MR when the cluster is full will wait for resources to be available before submitting a job. This is because the hadoop jar command is the primary mechanism Hive uses to know if a job is complete or failed.
Hive-on-Spark will timeout after {{SPARK_RPC_CLIENT_CONNECT_TIMEOUT}} because the RPC client in the AppMaster doesn't connect back to the RPC Server in HS2.
This is a behavior difference it'd be great to close.
was:
My understanding is as follows:
Hive-on-MR when the cluster is full will wait for resources to be available before submitting a job. This is because the hadoop jar command is the primary mechanism Hive uses to know if a job is complete.
Hive-on-Spark will timeout after {{SPARK_RPC_CLIENT_CONNECT_TIMEOUT}} because the RPC client in the AppMaster doesn't connect back to the RPC Server in HS2.
This is a behavior difference it'd be great to close.
> HOS times out when cluster is full while Hive-on-MR waits
> ---------------------------------------------------------
>
> Key: HIVE-20506
> URL: https://issues.apache.org/jira/browse/HIVE-20506
> Project: Hive
> Issue Type: Improvement
> Reporter: Brock Noland
> Priority: Major
>
> My understanding is as follows:
> Hive-on-MR when the cluster is full will wait for resources to be available before submitting a job. This is because the hadoop jar command is the primary mechanism Hive uses to know if a job is complete or failed.
>
> Hive-on-Spark will timeout after {{SPARK_RPC_CLIENT_CONNECT_TIMEOUT}} because the RPC client in the AppMaster doesn't connect back to the RPC Server in HS2.
> This is a behavior difference it'd be great to close.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)