[
https://issues.apache.org/jira/browse/BOOKKEEPER-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15616470#comment-15616470
]
Enrico Olivelli commented on BOOKKEEPER-912:
--------------------------------------------
in my case a cluster of Bookies is used by many different applications with
very different workloads
> Allow EnsemblePlacementPolicy to choose bookies using ledger custom data
> (multitenancy support)
> -----------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-912
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-912
> Project: Bookkeeper
> Issue Type: New Feature
> Components: bookkeeper-client
> Affects Versions: 4.4.0
> Reporter: Enrico Olivelli
> Assignee: Enrico Olivelli
> Fix For: 4.5.0
>
>
> I would like to restrict the set of bookies to be used for a specific ledger.
> Actually a single EnsemblePlacementPolicy is used for all the ledgers.
> This is because I want to create a ledger only using a dedicated set of
> machines/bookies which are dedicated to the 'tenant' for which I'm creating
> the ledger.
> We can add an optional (byte[]) parameter to asyncCreateLedger which in turn
> is to be passed to the configured EnsemblePlacementPolicy which in turn will
> be able to decide which are the most suitable bookies for the tenant.
> This parameter must be stored on ledger metadata, in order to be used in
> replaceBookie.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
