[
https://issues.apache.org/jira/browse/BOOKKEEPER-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659724#comment-13659724
]
Sijie Guo commented on BOOKKEEPER-592:
--------------------------------------
{quote}
ensemblePlacementPolicy=com.foobar.myCustomPolicy.class in the config
{quote}
will make it configurable and constructed by reflection.
{quote}
so why not keep the list of bookies in the BookieWatcher, and then pass them to
newEnsemble and replaceBookie on invokation?
{quote}
if keeping the list of bookies in the watcher, each time newEnsemble or
replaceBookie needs to rebuilt the topology of the list of bookies, which it
might be an expensive operation for some implementations (e.g. built rack
topology).
> allow application to recommend ledger data locality
> ---------------------------------------------------
>
> Key: BOOKKEEPER-592
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-592
> Project: Bookkeeper
> Issue Type: Improvement
> Reporter: Ming Ma
> Assignee: Sijie Guo
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-592.patch
>
>
> For application like hbase WAL, it will be useful if application like hbase
> can give a hint to bk about application's preferred ledger location. In that
> way, application can fail over to specific machines where one of the ledger
> replica is located; the recovery time will be faster. Another scenario is
> hbase's support for hot standby region server where read request can be
> served from a different machine other than the active region server. That
> requires the hot standby region server to read from ledger. If the ledger is
> on the same machine as standby region server, the performance will be better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
