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

Ted Yu commented on HBASE-15370:
--------------------------------

I searched my Inbox but didn't find the above comment. Assuming the above 
comment was made at 9:32 AM today, search-hadoop should have indexed it.

bq. Backport should be done by someone who knows MOB.

I have been reviewing MOB related code, porting it to branch-1, running MOB 
related tests, etc.
Of course there're people who are more familiar with MOB code. And I am fully 
open to their reviewing the backport patch.

bq.  there should be no new flakies in branch-1

I agree. That's was why I ran whole test suite (which passed) before attaching 
patch here. The backport patch should run through multiple QA runs before being 
considered stable.

bq. I see notes that TestMobExportSnapshot has failed a few times (that is 
probably because the test it derives from is flakey)

The test it derives from seems to be flaky. Let me loop TestMobExportSnapshot 
and TestMobRestoreFlushSnapshotFromClient on Linux to see if they fail with the 
backport.

> Backport Moderate Object Storage (MOB) to branch-1
> --------------------------------------------------
>
>                 Key: HBASE-15370
>                 URL: https://issues.apache.org/jira/browse/HBASE-15370
>             Project: HBase
>          Issue Type: Task
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>             Fix For: 1.4.0
>
>         Attachments: HBASE-15370-branch-1.v1.patch
>
>
> MOB feature was integrated to master branch 1 year ago.
> Since then there have been bug fixes which stabilize the feature.
> Some customers have been using it at PB scale.
> Here is discussion thread on dev mailing list:
> http://search-hadoop.com/m/YGbbDSqxD1PYXK62/hbase+MOB+in+branch-1&subj=Re+MOB+in+branch+1+Re+RESULT+VOTE+Merge+branch+hbase+11339+HBase+MOB+to+trunk+
> This issue is to backport MOB feature to branch-1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to