Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
v2.6.0
-
None
Description
When we restart the Kylin instance, due to the slow start of kylin, some monitoring scripts fail to detect the surviving kylin, and will also start the kylin instance. As a result, there are multiple kylin instances on a node.
By adding a file lock to the startup script (kylin.sh), it is guaranteed that only one kylin instance will be started when concurrent startup on a node.
Attachments
Issue Links
- links to