[
https://issues.apache.org/jira/browse/HIVE-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969169#action_12969169
]
He Yongqiang commented on HIVE-1837:
------------------------------------
Even adding a new SecurityManager, it won't work because the the main thread is
already dead (interrupted by another one).
> 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.
