[
https://issues.apache.org/jira/browse/BOOKKEEPER-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkateswararao Jujjuri (JV) updated BOOKKEEPER-1041:
-----------------------------------------------------
Description:
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.
was:
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 HDDs, as each HDD 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.
> 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)
