Hi 赵科,
Currently, RocketMQ uses mincore system call to determine if the message data
is in memory or swapped out. It seems more reliable than judging hot and cold
data based on the maintenance experience described in your proposal. And
turning off read-ahead for old CommitLog is a good idea,
+1
At 2023-03-07 14:55:05, "2017赵科" <464473...@qq.com.INVALID> wrote:
>Hi, RocketMQ Community,
>
>
>As discussed in the previous email, we launched a new RIP[RIP-62] Cold read
>control to support this feature. Now thei...@foxmail.com
>is willing to support the RIP, so I think it is time to start
Hi, thanks for the RIP.
Actually, rocketmq already has two configurations to control the cold read
behavior limitedly: maxTransferCountOnMessageInDisk
and maxTransferBytesOnMessageInDisk.
I have no idea how to handle these two configurations in your RIP, do you
plan to remove them or cooperate
+1
> 2023年3月7日 14:55，2017赵科 <464473...@qq.com.INVALID> 写道：
>
> Hi, RocketMQ Community,
>
>
> As discussed in the previous email, we launched a new RIP[RIP-62] Cold read
> control to support this feature. Now thei...@foxmail.com
> is willing to support the RIP, so I think it is time to start
GitHub user socutes added a comment to the discussion: Whether the
ForwardRequestProcessors are being used？
ok
GitHub link:
https://github.com/apache/rocketmq/discussions/6274#discussioncomment-5241433
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe,
GitHub user RongtongJin added a comment to the discussion: Whether the
ForwardRequestProcessors are being used？
Hi @socutes , I think this class is useless, you can subbmit a pull request to
delete the class.
GitHub link:
GitHub user RongtongJin edited a comment on the discussion: 关于过期文件删除问题
>
GitHub user RongtongJin added a comment to the discussion: 关于过期文件删除问题
>
