Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 21 Dec 2011 12:21:34 +0000 (UTC)
From: "Hudson (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <195435516.35099.1324470094101.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2078242437.10395.1323856351448.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5021) Enforce upper bound on timestamp
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HBASE-5021:
-------------------------------

Integrated in HBase-TRUNK-security #39 (See [https://builds.apache.org/job/HBase-TRUNK-security/39/])
    HBASE-5021 Enforce upper bound on timestamp
[jira] [HBase-5021] Enforce upper bound on timestamp

Summary:
We have been getting hit with performance problems on the ODS
side due to invalid timestamps being inserted by the timestamp.  ODS is
working on adding proper checks to app server, but production
performance could be severely impacted with significant recovery time if
something slips past.  Therefore, we should also allow the option to
check the upper bound in HBase.

This is the first draft.  Probably should allow per-CF customization.

Test Plan:  - mvn test -Dtest=TestHRegion#testPutWithTsTooNew

Reviewers: Kannan, Liyin, JIRA

CC: stack, nspiegelberg, tedyu, Kannan, mbautin

Differential Revision: 849

stack : 
Files : 
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java

                
> Enforce upper bound on timestamp
> --------------------------------
>
>                 Key: HBASE-5021
>                 URL: https://issues.apache.org/jira/browse/HBASE-5021
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Nicolas Spiegelberg
>            Assignee: Nicolas Spiegelberg
>            Priority: Critical
>             Fix For: 0.94.0
>
>         Attachments: 5021-addendum.txt, D849.1.patch, D849.2.patch, D849.3.patch, HBASE-5021-trunk.patch
>
>
> We have been getting hit with performance problems on our time-series database due to invalid timestamps being inserted by the timestamp.  We are working on adding proper checks to app server, but production performance could be severely impacted with significant recovery time if something slips past.  Since timestamps are considered a fundamental part of the HBase schema & multiple optimizations use timestamp information, we should allow the option to sanity check the upper bound on the server-side in HBase.

--
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