[
https://issues.apache.org/jira/browse/ROCKETMQ-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171070#comment-16171070
]
ASF GitHub Bot commented on ROCKETMQ-286:
-----------------------------------------
Github user dongeforever commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/162
@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);
}
```
> Add a switch to decide whether to wake up commitLogService when put message
> ---------------------------------------------------------------------------
>
> Key: ROCKETMQ-286
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-286
> Project: Apache RocketMQ
> Issue Type: Improvement
> Components: rocketmq-store
> Affects Versions: 4.0.0-incubating, 4.1.0-incubating
> Reporter: Eric Liu
> Assignee: Eric Liu
> Fix For: 4.2.0-incubating
>
>
> Now, it will wake up commitLogService after putting message. This may have
> impact on disk.
> Add a switch to control this feature.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
