hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18135) Track file archival for low latency space quota with snapshots
Date Fri, 16 Jun 2017 16:39:00 GMT

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

Hadoop QA commented on HBASE-18135:

| (x) *{color:red}-1 overall{color}* |
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 3s {color} | {color:red}
HBASE-18135 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.3.0/precommit-patchnames
for help. {color} |
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12873310/HBASE-18135.001.patch
| JIRA Issue | HBASE-18135 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/7204/console |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |

This message was automatically generated.

> Track file archival for low latency space quota with snapshots
> --------------------------------------------------------------
>                 Key: HBASE-18135
>                 URL: https://issues.apache.org/jira/browse/HBASE-18135
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 3.0.0
>         Attachments: HBASE-18135.001.patch
> Related to the work proposed on HBASE-17748 and building on the same idea as HBASE-18133,
we can make the space quota tracking for HBase snapshots faster to respond.
> When snapshots are in play, the location of a file (whether in the {{data}} or {{archive}}
directory) plays a factor in the realized size of a table. Like flushes, compactions, etc,
moving files from the data directory to the archive directory is done by the RegionServer.
We can hook into this call and send the necessary information to the Master so that it can
more quickly update the size of a table when there are snapshots in play.
> This will require the RegionServer to report the full coordinates of the file being moved
(table+region+family+file) so that the SnapshotQuotaObserverChore running in the master can
avoid HDFS lookups in partial or total to compute the location of a Region's hfiles.
> This may also require some refactoring of the SnapshotQuotaObserverChore to de-couple
the receipt of these file archival reports from RegionServers (e.g. {{HRegionFileSystem.removeStoreFiles(..)}},
and the Master processing the sizes of snapshots.

This message was sent by Atlassian JIRA

View raw message