[
https://issues.apache.org/jira/browse/BOOKKEEPER-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675857#comment-13675857
]
Ivan Kelly commented on BOOKKEEPER-592:
---------------------------------------
Regarding the hadoop-commons dependency, it seems the import you use have
almost no dependencies on anything else, and as such, we can just copy the code
itself over and include it in our tree without pulling in all the other stuff
hadoop-commons has. It has the problem that it will be hard to get fixes to
this code, but it does mean much easier maintenance of LICENCE and NOTICE, and
a much smaller dependency tree.
https://github.com/ivankelly/bookkeeper/tree/topology-from-hadoop/bookkeeper-server/src/main/java/org/apache/bookkeeper/util/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, BOOKKEEPER-592.patch,
> 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
