I have obeserved that when the "kylin.job.max-concurrent-jobs" properties is used for a cluster configuration and set to for e.g. lets say value 1. Then for a given cube building job cluster, during a cube build if another cube build request is submitted the currently running job is set to pending and Kylin starts running the new job on the same cluster. Then again it might pause the running job and any step and then return to the execution of the first job. This is usually observed after the first step but can be random.
Is this expected behavior? The good thing is ultimately both jobs run to success. Please share any knowledge on this. thanks! -- Sent from: http://apache-kylin.74782.x6.nabble.com/
