[
https://issues.apache.org/jira/browse/BOOKKEEPER-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641894#comment-13641894
]
Flavio Junqueira commented on BOOKKEEPER-592:
---------------------------------------------
Suggesting a set of bookies or bookie properties (e.g., rack locality) to drive
the selection of bookies when creating a ledger is not hard to do, it is mostly
a problem of designing the API change. One difficulty I'm seeing is that we
might end up diverging if there are bookie crashes and we change the ensemble.
We would need to keep that information with the metadata and use it to drive
the selection when replacing bookies.
> 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
>
> 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
