[
https://issues.apache.org/jira/browse/HBASE-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444484#comment-13444484
]
stack commented on HBASE-6659:
------------------------------
I thought about putting it into zk. The good thing is that it'd be persisted
so would make it across a master failover. In general the less footprint in
zk, the better. If we went this route, it'd be a znode per region on the
cluster. We'd write this region znode every time we flush. During high write
times could flush a file per second or so.... If 100k regions on cluster...
could be a bunch of zk writes.
I suppose an rpc to the master to ask it about a long that its keeping in an
in-memory map is way cheaper than going to fs, finding the region, and getting
the sequenceid out of the hfile metadata.
> Port HBASE-6508 Filter out edits at log split time
> --------------------------------------------------
>
> Key: HBASE-6659
> URL: https://issues.apache.org/jira/browse/HBASE-6659
> Project: HBase
> Issue Type: Bug
> Reporter: Zhihong Ted Yu
> Assignee: Zhihong Ted Yu
> Fix For: 0.96.0
>
> Attachments: 6508-v2.txt, 6508-v3.txt, 6508-v4.txt, 6508-v5.txt
>
>
> HBASE-6508 is for 0.89-fb branch.
> This JIRA ports the feature to trunk.
--
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
