[
https://issues.apache.org/jira/browse/ACCUMULO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270303#comment-13270303
]
Scott Kuehn commented on ACCUMULO-488:
--------------------------------------
The default timeout is 10 minutes, so the iterators in the InputFormat's
RecordReaders would have to exceed this amount when returning a single record
(progress is reported implicitly when a mapper receives a record). I suppose
AccumuloRowInputFormat is more of a risk if a row has lots of cells, but 10 min
still seems like plenty of time.
Since waiting more than 10 minutes for a single record is somewhat abnormal,
users that anticipate this behavior could set the timeout threshold by
adjusting the 'mapreduce.task.timeout' variable in their Job. Set it to 0 and
the task won't timeout.
Is there a scenario that I'm missing? If not, I think this ticket could be
closed out -- perhaps just mentioning the timeout var in the javadocs.
> InputFormats' RecordReaders should call Context.progress
> --------------------------------------------------------
>
> Key: ACCUMULO-488
> URL: https://issues.apache.org/jira/browse/ACCUMULO-488
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0, 1.3.5
> Reporter: John Vines
> Labels: newbie
> Fix For: 1.4.1
>
>
> The RecordReader for both input formats never call Context.progress(). This
> can leave long-running tasks timing out while still making progress.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
