[ 
https://issues.apache.org/jira/browse/HBASE-11339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119366#comment-14119366
 ] 

ramkrishna.s.vasudevan commented on HBASE-11339:
------------------------------------------------

The very first thought of some one wanting to store a KV that is bigger in size 
(I mean 100s of KBs to few MBs - 1 or 2 MB) makes one think if HBase could be 
the ideal choice.  The first think comes to mind is that write the references 
in HBase and the files in HDFS. But getting making this atomic itself needs 
some external things to monitor this.  Also the HBase features like snapshot 
and security may come inbuilt when we go with an approach of using HBase only 
and leveraging all its features.  If you see the discussion thread there were 
questions on writing the MOB part in the WAL and again in the HFiles. But all 
of the arguments had the pros and cons and finally the decision was made just 
because using HBase and leveraging its feature to support this MOB rather than 
external process and integrations helped us arrive in this decision.
I think Jon's nice write up is pretty much explains it.  
We had spent good amount of time since Jingcheng had proposed the feature and 
later in the reviews.  Having an MR tool (external) to control the MOB files 
came up even in internal discussion. For now we did not have a direct work 
around for that but HBASE-11861 is for solving this problem. 
Another advantage I would see here is that the snapshot feature that would work 
even with MOB. I think that would make this a clear winner instead of having to 
write another application that would do this MOB snapshot if HBase+HDFS would 
be used.
Adding to Anoop's comments we have reviewed the core patch HBASE-11643 that 
provides the basic things needed for MOB support and we are ready for a commit 
with 3 +1s to it.

> 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, 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)

Reply via email to