[jira] [Updated] (HBASE-5021) Enforce upper bound on timestamp

["Phabricator (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phabricator updated HBASE-5021:
-------------------------------

    Attachment: D849.1.patch

nspiegelberg requested code review of "[jira] [HBase-5021] Enforce upper bound on timestamp".
Reviewers: Kannan, Liyin, JIRA

  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

REVISION DETAIL
  https://reviews.facebook.net/D849

AFFECTED FILES
  src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
  src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.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: D849.1.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