hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramkrishna.S.Vasudevan" <ramkrishna.vasude...@huawei.com>
Subject FW: [jira] [Commented] (HBASE-5010) Filter HFiles based on TTL
Date Tue, 06 Mar 2012 08:49:45 GMT

Why HBASE-5510 updates coming in this JIRA?


-----Original Message-----
From: Hudson (Commented) (JIRA) [mailto:jira@apache.org] 
Sent: Tuesday, March 06, 2012 11:27 AM
To: ramakrishnas@huawei.com
Subject: [jira] [Commented] (HBASE-5010) Filter HFiles based on TTL

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

Hudson commented on HBASE-5010:

Integrated in HBase-TRUNK-security #129 (See [https://builds.apache.org/job/HBase-TRUNK-security/129/])
    HBASE-5010 Pass region info in LoadBalancer.randomAssignment(List<ServerName> servers)
(Anoop Sam John) (Revision 1297155)

     Result = FAILURE
tedyu : 
Files : 
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/DefaultLoadBalancer.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/LoadBalancer.java

> Filter HFiles based on TTL
> --------------------------
>                 Key: HBASE-5010
>                 URL: https://issues.apache.org/jira/browse/HBASE-5010
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Mikhail Bautin
>            Assignee: Mikhail Bautin
>             Fix For: 0.94.0
>         Attachments: 5010.patch, D1017.1.patch, D1017.2.patch, D909.1.patch, D909.2.patch,
D909.3.patch, D909.4.patch, D909.5.patch, D909.6.patch
> In ScanWildcardColumnTracker we have
> {code:java}
>   this.oldestStamp = EnvironmentEdgeManager.currentTimeMillis() - ttl;
>   ...
>   private boolean isExpired(long timestamp) {
>     return timestamp < oldestStamp;
>   }
> {code}
> but this time range filtering does not participate in HFile selection. In one real case
this caused next() calls to time out because all KVs in a table got expired, but next() had
to iterate over the whole table to find that out. We should be able to filter out those HFiles
right away. I think a reasonable approach is to add a "default timerange filter" to every
scan for a CF with a finite TTL and utilize existing filtering in StoreFile.Reader.passesTimerangeFilter.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message