[
https://issues.apache.org/jira/browse/HBASE-11339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120943#comment-14120943
]
Andrew Purtell commented on HBASE-11339:
----------------------------------------
{quote}
bq. The master's built in splitting was still available even if there was no MR
runtime that could run the replay tool.
If you were ok with 10 hr downtimes due to recovery (back then no meta first
recovery), the sure. For large deployments that MR for this was critical and
not really optional.
{quote}
It was possible if (perhaps deeply) suboptimal. We should expect the same with
MOB compaction, perhaps the first cut it's better to use the MR tool, but we
should not mandate the presence of the MR runtime for core HBase function.
> HBase MOB
> ---------
>
> Key: HBASE-11339
> URL: https://issues.apache.org/jira/browse/HBASE-11339
> Project: HBase
> Issue Type: Umbrella
> Components: regionserver, Scanners
> Reporter: Jingcheng Du
> Assignee: Jingcheng Du
> Attachments: HBase MOB Design-v2.pdf, HBase MOB Design-v3.pdf, HBase
> MOB Design-v4.pdf, HBase MOB Design.pdf, MOB user guide.docx, MOB user
> guide_v2.docx, MOB user guide_v3.docx, hbase-11339-in-dev.patch
>
>
> It's quite useful to save the medium binary data like images, documents
> into Apache HBase. Unfortunately directly saving the binary MOB(medium
> object) to HBase leads to a worse performance since the frequent split and
> compaction.
> In this design, the MOB data are stored in an more efficient way, which
> keeps a high write/read performance and guarantees the data consistency in
> Apache HBase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
