[ROCKETMQ-286] Add a switch to decide whether to wake up commitLogService when put message

[vsair]

Wake up commitLogService will make messages consumed quicker when put message, but it may increase disk usage. So, add a switch to decide where to open this feature, described in https://issues.apache.org/jira/browse/ROCKETMQ-286.

Brief change log

Add a config property to MessageStoreConfig

Verifying this change

Just a switch, verifying is to change it's value.

Follow this checklist to help us incorporate your contribution quickly and easily:

• Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Format the pull request title like [ROCKETMQ-XXX] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exists. If the new feature or significant change is committed, please remember to add integration-test in test module.
• Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

[vsair]

@zhouxinyu @lizhanhui @vongosling pls have a review.

[coveralls]

Coverage decreased (-0.2%) to 38.636% when pulling 6bc0b58 on vsair:ROCKETMQ-286 into 254d432 on apache:develop.

[vongosling]

@vsair Could you follow our new PR style for this PR, like #152

[vsair]

@vongosling I'v modified the description.

[vsair]

@zhouxinyu @vongosling pls have a review ?

[zhouxinyu]

LGTM, wake up commitLogService is for real-time, but it may let broker suffer from SSD write amplification, so provide a switch is reasonable.

[dongeforever]

@vsair @zhouxinyu another config flushCommitLogTimed has already handled such situation, and avoided SSD write amplification.
If flushCommitLogTimed is enabled, it will only wakeup the commitLogService, but could not wakeup the flushCommitLogService, for:

 if (flushCommitLogTimed) {
      Thread.sleep(interval);
 } else {
      this.waitForRunning(interval);
}

[zhouxinyu]

This PR is for ConsumeQueue, and flushCommitLogTimed is only used by FlushCommitLogService

[vongosling]

@vsair What happened in progress

[vsair]

@dongeforever yeah, it's right, I closed the PR.