[
https://issues.apache.org/jira/browse/BOOKKEEPER-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sijie Guo resolved BOOKKEEPER-950.
----------------------------------
Resolution: Fixed
Issue resolved by merging pull request 93
[https://github.com/apache/bookkeeper/pull/93]
{noformat}
commit 0583175de72446d00088611000310b000e8e61df
Author: Rithin <[email protected]>
AuthorDate: Tue Mar 28 13:35:30 2017 -0700
Commit: Sijie Guo <[email protected]>
CommitDate: Tue Mar 28 13:35:30 2017 -0700
BOOKKEEPER-950: Ledger placement policy to accomodate different storage
capacity of bookies
…ge capacity of bookies
This change introduces Disk weight based ledger placement. Currently free
disk space is the only supported
weight for a bookie. This change also introduces a new protocol message
between bk client and server
called GET_BOOKIE_INFO. This message is used by the client to retrieve the
free disk space info from
all the bookies. The existing placement policies: DefaultPlacementPolicy
and RackAwarePlacementPolicy
have been enhanced to make use of the weight while selecting bookies. New
test cases have been added to
test RackawarePlacement with weights. A new test class has been added to
test the weight based selection
algorithm in a stand alone fashion.
Author: Rithin <[email protected]>
Reviewers: Enrico Olivelli <[email protected]>, Sijie Guo
<[email protected]>
Closes #93 from rithin-shetty/weightBasedPlacementDec13
{noformat}
> 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)
