[
https://issues.apache.org/jira/browse/HBASE-5699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268110#comment-13268110
]
stack commented on HBASE-5699:
------------------------------
@Li You should be able to work whereever you like if you make up an harness for
running hlog implementations apart from hbase. This should be first order of
business (unless you are a masochist). Should be easy enough, if its not
possible already, especially after you make it pluggable.
Regards... "I'm assuming we don't need to guarantee HLog edit sequencing. If we
do, this becomes a bit harder." -- well thats the way it is currently so onus
will be on you to come up a reason why it could be otherwise. In-order makes it
easier to reason about whether or not all edits up to a particular sequence id
have been sync'd or not.
And don't forget the other side of the moon, the (distributed) log splitting
story. That needs to work too after you are done.
> Run with > 1 WAL in HRegionServer
> ---------------------------------
>
> Key: HBASE-5699
> URL: https://issues.apache.org/jira/browse/HBASE-5699
> Project: HBase
> Issue Type: Improvement
> Reporter: binlijin
> Assignee: Li Pi
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
