hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Thusoo (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-690) ScriptOperator still times out
Date Fri, 24 Jul 2009 20:49:14 GMT

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

Ashish Thusoo commented on HIVE-690:
------------------------------------

That is my bad. 

We should just fix this by reading stderr from the spawned process and sending updates to
the tracker if something has been written to stderr instead of indefinitely sending updates
as that may lead to processes not getting cleaned up?


> 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
>             Fix For: 0.4.0
>
>         Attachments: HIVE-690.1.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