[
https://issues.apache.org/jira/browse/BOOKKEEPER-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662846#comment-13662846
]
Ivan Kelly commented on BOOKKEEPER-592:
---------------------------------------
{quote}
since cluster change is passed to EnsemblePlacementPolicy, it would be easy to
getBookies from policy. Otherwise, two copies of bookies list need to be kept,
one in bookie watcher, the other one in ensemble policy. I don't know how to
handle this part gracefully, so I just add #getBookies interface in
PlacementPolicy.{quote}
One way would be to have BookieWatcher#getBookies read the bookies directly
rather than returning the previously read list.
> 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, 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
