[
https://issues.apache.org/jira/browse/KYLIN-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172237#comment-17172237
]
Gabor Arki commented on KYLIN-4348:
-----------------------------------
Altogether we have 10 running jobs in the cluster which show no progress:
* 169f75fa-a02f-221b-fc48-037bc7a842d0
* 0b5dae1b-6faf-66c5-71dc-86f5b820f1c4
* 00924699-8b51-8091-6e71-34ccfeba3a98
* 4620192a-71e1-16dd-3b05-44d7f9144ad4
* 416355c2-a3d7-57eb-55c6-c042aa256510
* 12750aea-3b96-c817-64e8-bf893d8c120f
* 42819dde-5857-fd6b-b075-439952f47140
* 00128937-bd4a-d6c1-7a4e-744dee946f67
* 46a0233f-217e-9155-725b-c815ad77ba2c
* 062150ba-bacd-6644-4801-3a51b260d1c5
However, the ones possessing the locks are all pending:
* f888380e-9ff4-98f5-2df4-1ae71e045f93
* fc186bd9-1186-6ed4-e58c-bbbf6dd8ef74
* d1a6475a-9ab2-5ee4-6714-f395e20cfc01
So, essentially the jobs that are running cannot actually run because they are
unable to acquire a lock. However, the ones that possess the lock cannot
continue because there are already 10 running jobs. This seems to be a deadlock
to me.
> Fix distributed concurrency lock bug
> ------------------------------------
>
> Key: KYLIN-4348
> URL: https://issues.apache.org/jira/browse/KYLIN-4348
> Project: Kylin
> Issue Type: Sub-task
> Reporter: wangxiaojing
> Assignee: wangxiaojing
> Priority: Major
> Fix For: v3.1.0
>
> Attachments: image-2020-02-03-10-54-21-976.png,
> image-2020-02-03-10-54-53-468.png
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
