[
https://issues.apache.org/jira/browse/KYLIN-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ma Gang updated KYLIN-1819:
---------------------------
Attachment: fix_swallow_scheduler_start_exception
1. don't use new thread to init the default scheduler, since the scheduler is a
must for the "JOB"/"ALL" mode kylin server, scheduler start in a new thread
make user not aware that the scheduler start fail.
2. remove the ConnectionStateListener interface from DefaultScheduler, since it
is complicated to implement HA for job engine.
> Exception swallowed when start DefaultScheduler fail
> ----------------------------------------------------
>
> Key: KYLIN-1819
> URL: https://issues.apache.org/jira/browse/KYLIN-1819
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
> Affects Versions: v1.5.1, v1.5.2
> Reporter: Ma Gang
> Assignee: Ma Gang
> Attachments: fix_swallow_scheduler_start_exception
>
>
> Start job scheduler need to acquire job lock from zookeeper, when lock
> acquire fail, it will throw an IllegalException, but because the scheduler is
> started in a new thread, the exception thrown by the thread will be ignored,
> and the server still started successfully, and no exceptions are logged. That
> make it hard for trouble shooting, should change to make server started fail
> when the scheduler started fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
