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

Eugene Koifman commented on HIVE-4808:
--------------------------------------

Couple of suggestions from Hadoop user list on setting timeout programmatically:

Yes, you can set it into your Job configuration object in code. If
your driver uses the Tool framework, then you can also pass a
-Dmapred.task.timeout=value CLI argument when invoking your program.
AND
'mapred.task.timeout' is deprecated configuration. You can use 
'mapreduce.task.timeout' property to do the same.
You could set this configuration while submitting the Job using 
org.apache.hadoop.conf.Configuration.setLong(String name, long value) API from 
conf or JobConf.
                
> WebHCat job submission is killed by TaskTracker since it's not sending a 
> heartbeat properly
> -------------------------------------------------------------------------------------------
>
>                 Key: HIVE-4808
>                 URL: https://issues.apache.org/jira/browse/HIVE-4808
>             Project: Hive
>          Issue Type: Bug
>          Components: HCatalog
>    Affects Versions: 0.11.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>             Fix For: 0.12.0
>
>         Attachments: HIVE-4808.patch
>
>
> (set mapred.task.timeout=70000)
> curl -i -d user.name=ekoifman \
> -d jar=/user/ekoifman/webhcate2e/hexamples.jar \
> -d class=sleep \
> -d arg="-mt" \
> -d arg="50000" \
> -d statusdir=/tmp \
> 'http://localhost:50111/templeton/v1/mapreduce/jar'
> The TempletonControllerJob gets retried 4 times (Thus there are 4 SleepJob 
> invocations) with message that it was killed due to inactivity.
> hexamples.jar = hadoop-examples-*.jar

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to