[
https://issues.apache.org/jira/browse/BOOKKEEPER-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611362#comment-13611362
]
Flavio Junqueira commented on BOOKKEEPER-593:
---------------------------------------------
I think that changing the internals shouldn't be difficult as you guys point
out. The part that might be a bit tricky is the changes to the API. How exactly
developers are supposed to express their preferences? In the case we can't
satisfy the user preferences, do we fail the request to create a ledger or we
move to selecting it arbitrarily? For example, say that the user expresses a
preference for at least one bookie in a given rack. If there is no such a
bookie in the bookie pool, do we fail the request or select another one
arbitrarily?
> use the application machine as one of bookies for ledger write if possible
> --------------------------------------------------------------------------
>
> Key: BOOKKEEPER-593
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-593
> Project: Bookkeeper
> Issue Type: Improvement
> Reporter: Ming Ma
>
> In the scenario where bk applications run on the same set of machines as
> bookies, it will be useful if bk can put one of the ledger replica on the
> same machine as the application. In that way one of the ledger writes will be
> local and could improve the performance.
--
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
