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 Thu, 27 Feb 2014 16:31:20 GMT

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

Billie Rinaldi updated YARN-1730:

    Attachment: YARN-1730.6.patch

Attaching a new patch with variables and methods renamed as suggested, and with the write
locking moved to the put method.  I think expanding the lock is the right thing to do.  I
didn't move the default cache sizes to YarnConfiguration yet, so let me know if you still
want me to do that.

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

View raw message