[
https://issues.apache.org/jira/browse/BOOKKEEPER-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615777#comment-15615777
]
Venkateswararao Jujjuri (JV) commented on BOOKKEEPER-912:
---------------------------------------------------------
I guess this feature is heading towards creating pools within the cluster.
That is great, so I can have a SSD pool and HDD pool, which I opened
BOOKKEEPER-950
Couple more:
- We need to make sure replication logic also aware/follows this.
- How many classifications/pools we can have?
- What is the order of placement or error handling scenario?
During replication, what if we can't find a bookie in the same pool to
replicate? do we stay under-replicated? or pick next
priority pool? If later, how long we keep it in non-ideal pool? how do we
move it back to ideal pool when/if space is available?
Alternatively I am thinking of having Ledger types. Currently all ledgers
behave/act same, We can do very interesting
things if we can comeup with ledger type, and tune each type separately for
specific workloads.
I will open a issue for that.
> 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)
