hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Namit Jain (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-410) Heartbeating for streaming jobs should not depend on stdout
Date Wed, 20 May 2009 18:20:45 GMT

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

Namit Jain commented on HIVE-410:

1. Why did you increase the max memory from 256 to 512 m ?
2. Instead of hard coding 5 minutes, can you make it a function of map reduce timeout (10
minutes in the above note)

> Heartbeating for streaming jobs should not depend on stdout
> -----------------------------------------------------------
>                 Key: HIVE-410
>                 URL: https://issues.apache.org/jira/browse/HIVE-410
>             Project: Hadoop Hive
>          Issue Type: Bug
>            Reporter: Venky Iyer
>            Assignee: Ashish Thusoo
>            Priority: Blocker
>         Attachments: patch-410.txt
> jobs that require iterative processing may take longer than 10 mins to produce rows.
This shouldn't be cause to kill the job. Producing keepalive dummy rows to stdout is bad if
the data has to go into a Hive table or other Hive steps.
> If we adopt the solution of using stderr to indicate heartbeats, can that be combined
with streaming counters (http://hadoop.apache.org/core/docs/current/streaming.html#How+do+I+update+counters+in+streaming+applications%3F
)? Also, will limitations on size of stderr break this?

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

View raw message