You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Charan Reddy Guttapalem (JIRA)" <ji...@apache.org> on 2017/06/02 00:23:04 UTC

[jira] [Commented] (BOOKKEEPER-1041) Multiple active entrylogs

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

Charan Reddy Guttapalem commented on BOOKKEEPER-1041:
-----------------------------------------------------

[~sijie@apache.org] created writeup for this work item and discussed about it in last community call (May 18th)

> Multiple active entrylogs
> -------------------------
>
>                 Key: BOOKKEEPER-1041
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1041
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-server
>            Reporter: Venkateswararao Jujjuri (JV)
>            Assignee: Charan Reddy Guttapalem
>
> Current bookkeeper is tuned for rotational HDDs. It has one active entrylog, and all the ledger/entries go to the same entrylog until it is rotated out. This is perfect for HDDs as seeks and moving head allover the disk platter is very expensive. But this is very inefficient for SSDs, as each SSD can handle multiple parallel writers, also this method is extremely inefficient for compaction as it causes write amplification and inefficient disk space usage.
> Our proposal is to have multiple active entrylogs and a configuration param on how many parallel entrylogs the system can have. This way one can have ability to configure to have less (may be  one) ledger per entrylog.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)