You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2018/10/12 02:00:00 UTC

[jira] [Updated] (KYLIN-3499) Double check timestamp in HBase when got "RetriesExhaustedException"

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

Shaofeng SHI updated KYLIN-3499:
--------------------------------
    Issue Type: Improvement  (was: Bug)
       Summary: Double check timestamp in HBase when got "RetriesExhaustedException"  (was: resource inconsistent caused by hbase rpc timeout)

> Double check timestamp in HBase when got "RetriesExhaustedException"
> --------------------------------------------------------------------
>
>                 Key: KYLIN-3499
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3499
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Storage - HBase
>    Affects Versions: all
>            Reporter: ulysses you
>            Assignee: ulysses you
>            Priority: Major
>             Fix For: v2.6.0
>
>         Attachments: ca7a61b2fdbfc321e7c896c3d34fd4d4c48e3eed.patch, error.png
>
>
> KYLIN use hbase to persist resouce metadata. When hbase rpc timeout, kylin would rollback the resource timestamp. It caused resource inconsistent between kylin's memory and hbase if hbase already put the resource.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)