[
https://issues.apache.org/jira/browse/MAPREDUCE-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117968#comment-15117968
]
Robert Kanter commented on MAPREDUCE-6613:
------------------------------------------
This seems like a good default to change:
- It has a ~2x speedup (see MAPREDUCE-6376)
- The parsing code already can handle either format
- I don't think we should worry about users catting the jhist file directly;
that's not an official stable "API". If someone really wants to do that, they
could set the config back to "json". Otherwise, defaulting to "binary" should
help the most number of users.
[~jlowe], what do you think?
> Change mapreduce.jobhistory.jhist.format default from json to binary
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-6613
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6613
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Affects Versions: 2.8.0
> Reporter: Ray Chiang
> Assignee: Ray Chiang
> Priority: Minor
> Attachments: MAPREDUCE-6613.001.patch
>
>
> MAPREDUCE-6376 added a configuration setting to set up .jhist internal format:
> mapreduce.jobhistory.jhist.format
> Currently, the default is "json". Changing the default to "binary" allows
> faster parsing, but with the downside of making the file not output friendly
> by using "hadoop fs cat".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
