[
https://issues.apache.org/jira/browse/HBASE-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444508#comment-13444508
]
Ted Yu commented on HBASE-6659:
-------------------------------
bq. or we could put it in a data structure apart from serverload
Do we have a route through which such data structure can be channeled to master
nowadays ?
bq. out of metrics w/ master pulling the info when its interested in particular
The use case for this feature is that log splitters may request sequence Ids in
a short period of time. I am not sure if I understand the above comment enough
in this context.
I agree with Stack's analysis on using zookeeper. In a large cluster under
heavy write load, sufficient experiment / profiling is needed to justify the
approach.
Again, the reason I came with the port was that I found this feature very
helpful, even if HBASE-5699 is implemented.
I think the patch didn't introduce fresh design deficiency.
I can address Stack's other comments in the next patch.
When there is good alternative to retiring heartbeat, all the payload can be
moved in one shot.
> 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
