[
https://issues.apache.org/jira/browse/BOOKKEEPER-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849176#comment-15849176
]
ASF GitHub Bot commented on BOOKKEEPER-950:
-------------------------------------------
Github user rithin-shetty commented on the issue:
https://github.com/apache/bookkeeper/pull/93
@eolivelli I have added a new test case for testing the timeout of
GET_BOOKIE_INFO op. See TestGetBookieInfoTimeout.java
> 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.15#6346)
