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

Posted to issues@kylin.apache.org by "ChangjiGuo (Jira)" <ji...@apache.org> on 2019/12/30 02:49:00 UTC

[jira] [Closed] (KYLIN-4318) Disconnection from the regionserver where the kylin metadata is located during the execution of the job will cause the job to fail to continue

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

ChangjiGuo closed KYLIN-4318.
-----------------------------
    Resolution: Not A Problem

> Disconnection from the regionserver where the kylin metadata is located during the execution of the job will cause the job to fail to continue
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KYLIN-4318
>                 URL: https://issues.apache.org/jira/browse/KYLIN-4318
>             Project: Kylin
>          Issue Type: Bug
>          Components: Job Engine
>    Affects Versions: v2.6.4
>         Environment: hadoop-version : 2.7.7
> hbase-version: 1.4.10
> kylin-version: 2.6.4-hbase-1x
>            Reporter: ChangjiGuo
>            Priority: Blocker
>         Attachments: image-2019-12-27-19-52-54-184.png
>
>
> Hello, I encountered the following problem:
>     During the job running, if disconnected from the regionserver where the metadata is located, the job status cannot be synchronized, the job will be stuck and job's status will display as running. I have reproduced this problem offline.
> How to reproduce ?
>     1. See which regionserver the table kylin_metadata is in.
>     2. Kill the hbase regionserver process while the job is running.
>     3. You can see the following log in kylin.lg:
> !image-2019-12-27-19-52-54-184.png!
>     4. The job will always be in running state and it has completed.
> I am trying to fix it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)