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

Hudson commented on MAPREDUCE-6141:
-----------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #6932 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/6932/])
MAPREDUCE-6141. History server leveldb recovery store. Contributed by Jason 
Lowe (jlowe: rev 56b7ec71a69820ae12b4b9e2eb04b7368f721dbf)
* 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/HistoryServerLeveldbStateStoreService.java
* 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml
* 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/test/java/org/apache/hadoop/mapreduce/v2/hs/TestHistoryServerLeveldbStateStoreService.java
* 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/pom.xml
* hadoop-mapreduce-project/CHANGES.txt
* 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/JHAdminConfig.java


> History server leveldb recovery store
> -------------------------------------
>
>                 Key: MAPREDUCE-6141
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6141
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>             Fix For: 2.7.0
>
>         Attachments: MAPREDUCE-6141.patch, MAPREDUCE-6141v2.patch, 
> MAPREDUCE-6141v2.patch
>
>
> It would be nice to have a leveldb option to the job history server recovery 
> store.  Leveldb would provide some benefits over the existing filesystem 
> store such as better support for atomic operations, fewer I/O ops per state 
> update, and far fewer total files on the filesystem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to