[
https://issues.apache.org/jira/browse/BOOKKEEPER-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15554587#comment-15554587
]
Enrico Olivelli commented on BOOKKEEPER-950:
--------------------------------------------
[~rithin.shetty] I understand your point.
In order to implement such an issue bookies should publish on ZK available disk
space and this information need to be passed to the placement policy or at
least we have to provide some out-of-the-box function to ask for current bookie
disk space availability.
> Ledger placement policy to accomodate different storage capacity of bookies
> ---------------------------------------------------------------------------
>
> Key: BOOKKEEPER-950
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-950
> Project: Bookkeeper
> Issue Type: New Feature
> Reporter: Rithin Shetty
> Assignee: Rithin Shetty
> Fix For: 4.5.0
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> In our environment, in Salesforce, we are likely to have bookie nodes with
> different storage capacity: some will have 1TB others might have 3TB. Also,
> our ledgers are likely going to be long lived. The current ledger placement
> policy selects the bookies randomly leading to uniform distribution. This
> would cause some of bookies to reach high utilization while the rest would be
> underutilized. We need a new ledger placement policy that has higher
> probability of selecting bookies with higher free disk space than the ones
> with lower disk free space.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
