hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zheng Shao (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-690) ScriptOperator still times out
Date Mon, 27 Jul 2009 17:54:14 GMT

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

Zheng Shao commented on HIVE-690:
---------------------------------

The old timer code was never useful because the timeout is the same as the expiry period,
so the behavior didn't change actually.

I think this is what we want. If we set it to true by default, it is very easy for some programs
to enter infinite loops and never finish.
We should enable it only with users' explicit command "set hive.script.auto.progress=true;".


> ScriptOperator still times out
> ------------------------------
>
>                 Key: HIVE-690
>                 URL: https://issues.apache.org/jira/browse/HIVE-690
>             Project: Hadoop Hive
>          Issue Type: Bug
>            Reporter: Zheng Shao
>            Assignee: Zheng Shao
>            Priority: Blocker
>             Fix For: 0.4.0
>
>         Attachments: HIVE-690.1.patch, HIVE-690.2.patch
>
>
> The code is using exp_interval instead of exp_int in the "scheduleAtFxiedRate".
> {code}
>       Integer exp_interval = null;
>       int exp_int;
>       exp_interval = Integer.decode(hconf.get("mapred.tasktracker.expiry.interval"));
>       if (exp_interval != null)
>         exp_int = exp_interval.intValue() / 2;
>       else
>         exp_int = 300000;
>       rpTimer = new Timer(true);
>       rpTimer.scheduleAtFixedRate(new ReporterTask(reporter), 0, exp_interval);
> {code}

-- 
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