[
https://issues.apache.org/jira/browse/HBASE-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445633#comment-13445633
]
stack commented on HBASE-6659:
------------------------------
There are a few approaches I think. We could hold up this patch till we figure
alternate channel for metrics and attributes -- e.g. have the master listen to
the metrics emitted by regionservers rather than have the regionserver blast
load out on a metrics channel and duplicate their compostion putting same info
out on the regionserver heartbeat -- or we commit the patch as is (after the
non-architectural issues raised in the issue have been addressed) and address
the messaging problems later.
It looks like it could help a bunch with MTTR even though its totally ugly the
way we are calling master up out of an HLog (how do you put that facility
behind an Interface?)
> 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
