[
https://issues.apache.org/jira/browse/BOOKKEEPER-916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkateswararao Jujjuri (JV) updated BOOKKEEPER-916:
----------------------------------------------------
Assignee: Rithin Shetty (was: Venkateswararao Jujjuri (JV))
> Placement policy to accomodate different types of ledger storage
> ----------------------------------------------------------------
>
> Key: BOOKKEEPER-916
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-916
> Project: Bookkeeper
> Issue Type: New Feature
> Components: bookkeeper-client, bookkeeper-server
> Affects Versions: 4.3.2
> Reporter: Venkateswararao Jujjuri (JV)
> Assignee: Rithin Shetty
>
> As we start to use bookkeeper as long term storage, it may not be right use
> of resources to keep all copies of entry (write ensemble) on efficient
> storage. This feature is to come up with an intelligent placement that
> distributes entry copies across different classes of storage.
> Simply put, say we have SSD based ledger storage and HDD based ledger storage
> on each system. Instead of putting all copies of entries either on SSD or on
> HDD, this placement policy maintains one copy on SSD and others on HDD.
> - Have at least one copy on SSD and others on HDD.
> - Writer need to be aware of this classification
> - Replication logic need to be aware of this logic.
> - While reading attempt to read from SSD first.
> - Reader also need to be aware of this logic.
> This will push bookkeeper towards the long term storage, also can be a
> stepping store towards introducing storage tiers in the future.
> This has dependency/relation to
> https://issues.apache.org/jira/browse/BOOKKEEPER-912.
> https://issues.apache.org/jira/browse/BOOKKEEPER-915
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
