hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-1837) optional timeout for hive clients
Date Tue, 07 Dec 2010 21:27:10 GMT

    [ https://issues.apache.org/jira/browse/HIVE-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969000#action_12969000
] 

Ashutosh Chauhan commented on HIVE-1837:
----------------------------------------

You get this feature for free when you move to secure Hadoop. A mapreduce job by default gets
a token which expires in 24 hrs. So, usually MR job spawned by Hive query will fail after
that time. Job may request renewal upto 7 days. Beyond that, special provisions are required.
So, timeout is inherently built into secure hadoop.

> optional timeout for hive clients
> ---------------------------------
>
>                 Key: HIVE-1837
>                 URL: https://issues.apache.org/jira/browse/HIVE-1837
>             Project: Hive
>          Issue Type: New Feature
>            Reporter: Namit Jain
>            Assignee: He Yongqiang
>         Attachments: hive-1837.1.patch, hive-1837.2.patch
>
>
> It would be a good idea to have a optional timeout for hive clients.
> We encountered a query today, which seemed to have run by mistake, and it was running
for about a month.
> This was holding zookeeper locks, and making the whole debugging more complex than it
should be.
> It would be a good idea to have a timeout for a hive client.
> @Ning, I remember there was some issue with the Hive client having a timeout of 1 day
with HiPal.
> Do you remember the details ?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message