KYLIN-3578 Condition replaces the use of the Object monitor methods

[hit-lacus]

Please refer to https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/locks/Condition.html

[asfgit]

Can one of the admins verify this patch?

[asfgit]

Can one of the admins verify this patch?

[coveralls]

Pull Request Test Coverage Report for Build 3653

• 0 of 8 (0.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.004%) to 23.125%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
core-common/src/main/java/org/apache/kylin/common/util/MemoryBudgetController.java	0	8	0.0%

Totals
Change from base Build 3650:	0.004%
Covered Lines:	16159
Relevant Lines:	69876

---

💛 - Coveralls

[hit-lacus]

Admin, please do not merge this commit, I will recheck my commit.

[hit-lacus]

if (delta < 0) {
     synchronized (lock) {
        lock.notifyAll();
    }
}

This code above seems violates good practice, but it's just a trick.So it is no need to repair it.

oracle locksync doc
Chinese Javadoc
Do not synchronize on the intrinsic locks of high-level concurrency objects