[
https://issues.apache.org/jira/browse/BOOKKEEPER-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677757#comment-15677757
]
ASF GitHub Bot commented on BOOKKEEPER-912:
-------------------------------------------
Github user eolivelli commented on the issue:
https://github.com/apache/bookkeeper/pull/68
The idea is that you can.implemement a custom policy which takes into
account the custometadata. I am going to use this feature at least for these
two cases:
1) for.multitenancy, that is that a ledger is created for a tenant/user and
the policy will choose the best bookies according to the user' SLA. The
internals of this policy is custom and depends on the project
2) in order to define different behaviors depending on the type of ledger.
I have many different applications/services that share the same BookKeeper
cluster and only one single policy can't work for every usecase. Using metadata
you can implement a custom policy which forwards request to other policies
depending on the specs written in metadata
> 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)
