You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/03/27 19:10:41 UTC
[jira] [Commented] (HBASE-17750) Update RS Chore that computes
Region sizes to avoid double-counting on rematerialized tables
[ https://issues.apache.org/jira/browse/HBASE-17750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943865#comment-15943865 ]
Hadoop QA commented on HBASE-17750:
-----------------------------------
| (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 9s {color} | {color:red} HBASE-17750 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/12860703/HBASE-17750.001.patch |
| JIRA Issue | HBASE-17750 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/6237/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> Update RS Chore that computes Region sizes to avoid double-counting on rematerialized tables
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-17750
> URL: https://issues.apache.org/jira/browse/HBASE-17750
> Project: HBase
> Issue Type: Sub-task
> Reporter: Josh Elser
> Assignee: Josh Elser
> Attachments: HBASE-17750.001.patch
>
>
> When a table is restored from a snapshot, it will reference files that are also referenced by the Snapshot (and potentially the source table). We need to make sure that these restored tables do not also "count" the size of those files as it would make the actual FS utilization incorrect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)