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

hejian edited comment on KYLIN-3964 at 4/23/19 9:27 AM:
--------------------------------------------------------

hi [~Shaofengshi], hard to repro in test environment, even try the updated 
version.

In recent days, this issue occurs frequently in formal environment with 
kylin-2.4.0, about 1 of 160 segments every day(the hbase connection timeout 
etc.) .

I wonder know how can i handle the bad segment through restful api rather than 
edit the metadata, and i think the final solution of KYLIN-2849 can help a lot 
but i can not find it. 


was (Author: hejian999):
hi [~Shaofengshi], hard to repro in test environment, even try the updated 
version.

In recent days, this issue occurs frequently in formal environment with 
kylin-2.4.0, about 1 of 160 segments every day(the hbase connection timeout 
etc.) .

I wonder know how can i handle the bad segment through restful api rather than 
edit the metadata, and i think the final solution of KYLIN-2849 can help a lot 
by i can not find the it even after read the related source code. 

> segment overlapped, the status is "NEW", last_build_job_id is null, can not  
> refresh/delete/build this segment
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: KYLIN-3964
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3964
>             Project: Kylin
>          Issue Type: Bug
>         Environment: kylin-2.4.0
>            Reporter: hejian
>            Priority: Major
>         Attachments: image-2019-04-22-10-07-06-737.png, 
> image-2019-04-23-16-51-34-805.png, image-2019-04-23-16-52-55-756.png
>
>
> *Any action* *involved* *this segment can not be excute by requesting api due 
> to no job_id provided.*
> !image-2019-04-22-10-07-06-737.png!
> merge/refresh/rebuild/delete does not work 
> !image-2019-04-23-16-51-34-805.png!!image-2019-04-23-16-52-55-756.png!



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

Reply via email to