[
https://issues.apache.org/jira/browse/HBASE-22749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895463#comment-16895463
]
stack commented on HBASE-22749:
-------------------------------
Skimmed PDF. Looks good. Why is it called MOB 2.0? Seems to be just a change in
compaction. Can we have a true 2.0? Streaming/Chunking of big values writing
smaller more hbase-friendly Cells that client aggregates rather than the
big-Cell abuse that currently is MOB?
On the first section:
* It says, "There is no more special compactor for MOB files", but the class
that is doing the compaction is named DefaultMobStoreCompactor; i.e. a
compactor that is 'default' but for 'MOB'?
* On #3, to compact MOB, need to submit a major_compaction request. Does that
mean we major compact all in the target table -- MOB and other files? Can I do
one or the other (MOB or HFiles). Operator has to manually run compactions?
(But next section describes a chore to do this?)
* After finishing 'Unified Compactor' section, how does this differ from what
was there before? Why superior?
... ok, done.
> HBase MOB 2.0
> -------------
>
> Key: HBASE-22749
> URL: https://issues.apache.org/jira/browse/HBASE-22749
> Project: HBase
> Issue Type: New Feature
> Components: mob
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Major
> Attachments: HBase-MOB-2.0-v1.pdf
>
>
> There are several drawbacks in the original MOB 1.0 (Moderate Object
> Storage) implementation, which can limit the adoption of the MOB feature:
> # MOB compactions are executed in a Master as a chore, which limits
> scalability because all I/O goes through a single HBase Master server.
> # Yarn/Mapreduce framework is required to run MOB compactions in a scalable
> way, but this won’t work in a stand-alone HBase cluster.
> # Two separate compactors for MOB and for regular store files and their
> interactions can result in a data loss (see HBASE-22075)
> The design goals for MOB 2.0 were to provide 100% MOB 1.0 - compatible
> implementation, which is free of the above drawbacks and can be used as a
> drop in replacement in existing MOB deployments. So, these are design goals
> of a MOB 2.0:
> # Make MOB compactions scalable without relying on Yarn/Mapreduce framework
> # Provide unified compactor for both MOB and regular store files
> # Make it more robust especially w.r.t. to data losses.
> # Simplify and reduce the overall MOB code.
> # Provide 100% compatible implementation with MOB 1.0.
> # No migration of data should be required between MOB 1.0 and MOB 2.0 - just
> software upgrade.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
