You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Navya Sruthi Sunkarapalli (JIRA)" <ji...@apache.org> on 2019/04/29 19:10:00 UTC

[jira] [Assigned] (HIVE-21649) Passing an non-existent jar in HIVE_AUX_JARS_PATH produces incorrect error message

     [ https://issues.apache.org/jira/browse/HIVE-21649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Navya Sruthi Sunkarapalli reassigned HIVE-21649:
------------------------------------------------

    Assignee: Navya Sruthi Sunkarapalli

> Passing an non-existent jar in HIVE_AUX_JARS_PATH produces incorrect error message
> ----------------------------------------------------------------------------------
>
>                 Key: HIVE-21649
>                 URL: https://issues.apache.org/jira/browse/HIVE-21649
>             Project: Hive
>          Issue Type: Bug
>          Components: Tez
>            Reporter: Todd Lipcon
>            Assignee: Navya Sruthi Sunkarapalli
>            Priority: Minor
>
> I had configured HS2 with HIVE_AUX_JARS_PATH pointing to a non-existent postgres jar. This resulted in queries failing with the following error:
> {code}
>  tez.DagUtils: Localizing resource because it does not exist: file:/data/1/todd/impala/fe/target/dependency/postgresql-42.2.5.jar to dest:
>    hdfs://localhost:20500/tmp/hive/todd/_tez_session_dir/9de357d5-59bf-4faa-8973-5212a08bc41a-resources/postgresql-42.2.5.jar
>  tez.DagUtils: Looks like another thread or process is writing the same file
>  tez.DagUtils: Waiting for the file hdfs://localhost:20500/tmp/hive/todd/_tez_session_dir/9de357d5-59bf-4faa-8973-5212a08bc41a-resources/postgresql-42.2.5.jar (5 attempts, with 5000ms interval)
>  tez.DagUtils: Could not find the jar that was being uploaded
> {code}
> This incorrect logging sent me on a wild goose chase looking for concurrency issues, HDFS issues, etc, before I realized that the jar in fact didn't exist on the local FS. This is due to some sketchy code which presumes that any IOException is due to a writing conflict.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)