kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KYLIN-3499) resource inconsistent caused by hbase rpc timeout
Date Tue, 21 Aug 2018 05:34:00 GMT

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

ASF GitHub Bot commented on KYLIN-3499:
---------------------------------------

momoxixi commented on issue #198: KYLIN-3499 Update HBaseResourceStore.java
URL: https://github.com/apache/kylin/pull/198#issuecomment-414554814
 
 
   In my Hadoop cluster, HDFS would occur `SLOW BlockReceiver xxx` sometimes, it  also made
HBase rpc slow. When HBase rpc timeout kylin rollback the resource timestamp but actually
HBase rpc already finished at server. So I added an another check to make sure HBase server
has not received that rpc.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> resource inconsistent caused by hbase rpc timeout
> -------------------------------------------------
>
>                 Key: KYLIN-3499
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3499
>             Project: Kylin
>          Issue Type: Bug
>          Components: Storage - HBase
>    Affects Versions: all
>            Reporter: ulysses you
>            Priority: Major
>             Fix For: Future
>
>         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)

Mime
View raw message