You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2016/02/18 02:23:18 UTC

[jira] [Commented] (HIVE-13051) Deadline class has numerous issues

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

Sergey Shelukhin commented on HIVE-13051:
-----------------------------------------

The main issue is that it appears that failure can keep the old timer running, resulting in failures on some subsequent check from another operation. 

> Deadline class has numerous issues
> ----------------------------------
>
>                 Key: HIVE-13051
>                 URL: https://issues.apache.org/jira/browse/HIVE-13051
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-13501.patch
>
>
> currentTimeMillis is not a correct way to measure intervals of time; it can easily be adjusted e.g. by ntpd. System.nanoTime should be used.
> It's also unsafe for failure cases, and doesn't appear to update from config updates correctly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)