hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1730) Leveldb timeline store needs simple write locking
Date Tue, 04 Mar 2014 14:47:21 GMT

     [ https://issues.apache.org/jira/browse/YARN-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Billie Rinaldi updated YARN-1730:
---------------------------------

    Description: 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.  (was: 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.)

> 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, 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