hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1730) Leveldb timeline store needs simple write locking
Date Tue, 25 Feb 2014 19:40:20 GMT

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

Zhijie Shen commented on YARN-1730:
-----------------------------------

bq. The hold count only returns the number of holds that have been obtained by the current
thread. So as soon as the current thread is done with the lock, it would drop the lock from
the lock map, which is not what we want.

Make sense. One minor comment: how about make CountReentrantLock extend ReentrantLock, in
which way the code should a bit cleaner?

> 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
>         Attachments: YARN-1730.1.patch, YARN-1730.2.patch, YARN-1730.3.patch
>
>
> The actual data writes are performed atomically in a batch, but a lock should be held
while identifying a start time for the entity, which precedes every write.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message