hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1730) Leveldb timeline store needs simple write locking
Date Wed, 05 Mar 2014 14:55:59 GMT

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

Hudson commented on YARN-1730:
------------------------------

SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1717 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1717/])
YARN-1730. Implemented simple write-locking in the LevelDB based timeline-store. Contributed
by Billie Rinaldi. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1574145)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/timeline/LeveldbTimelineStore.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/timeline/TestLeveldbTimelineStore.java


> Leveldb timeline store needs simple write locking
> -------------------------------------------------
>
>                 Key: YARN-1730
>                 URL: https://issues.apache.org/jira/browse/YARN-1730
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>             Fix For: 2.4.0
>
>         Attachments: YARN-1730.1.patch, YARN-1730.2.patch, YARN-1730.3.patch, YARN-1730.4.patch,
YARN-1730.5.patch, YARN-1730.6.patch
>
>
> Although the leveldb writes are performed atomically in a batch, a start time for the
entity needs to identified before each write.  Thus a per-entity write lock should be acquired.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message