[
https://issues.apache.org/jira/browse/BOOKKEEPER-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647247#comment-13647247
]
Rakesh R commented on BOOKKEEPER-593:
-------------------------------------
Its an interesting topic:), basically the idea is to schedule the I/O intensive
operations closer to the data.
As I understood BOOKKEEPER-592, is talking the read I/O, which will helps
application to improve the fail-over time. But BOOKKEEPER-593, is talking about
the write centric data locality, here I feel the advantage we are getting with
BOOKKEEPER-592 will be in tose. By seeing these two usecases, bk should allow
users to set preferences/intelligence considering both these aspects?
bq. the write might be 0-(A,B), 1-(A, C), 2-(A, B).
Here machine A would be consumed more, I'm bit worried about the storage space
and requires an efficient load balancing algo. What do you say?
> 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
> Assignee: Sijie Guo
>
> 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
