You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "wysobj (via GitHub)" <gi...@apache.org> on 2023/08/23 07:08:58 UTC
[GitHub] [rocketmq] wysobj opened a new issue, #7233: [Bug] SYNC_FLUSH broker take a long bootstrap time
wysobj opened a new issue, #7233:
URL: https://github.com/apache/rocketmq/issues/7233
### Before Creating the Bug Report
- [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions).
- [X] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate.
- [X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
### Runtime platform environment
Ubuntu 22.04.2 LTS
### RocketMQ version
4.9.x
### JDK Version
1.8
### Describe the Bug
master-slave broker with SYNC_FLUSH mode, when send messages with PROPERTY_WAIT_STORE_MSG_OK set to false, StoreCheckpoint.physicMsgTimestamp is never updated.
The above bug cause `physicMsgTimestamp` in checkpoint file is always zero value. After a broker master node restart, the broker read zero value from checkpoint file in recover proceduer and scan from the first commitLog file, which lead to a very long bootstrap time.
### Steps to Reproduce
1. create a master-slave rocketmq broker group with SYNC_FLUSH
2. send messages with PROPERTY_WAIT_STORE_MSG_OK set to false
3. the StoreCheckpoint.physicMsgTimestamp won't be updated in flush procedure
4. restart master broker node, and the recover proceduer will scan from the first commitLog, because physicMsgTimestamp is zero value
### What Did You Expect to See?
The physicMsgTimestamp in checkpoint file is correct and broker will skip the preceeding commitLog files before physicMsgTimestamp
### What Did You See Instead?
physicMsgTimestamp in checkpoint file is zero, and broker recover scan from the first commitLog file
### Additional Context
No response
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] SYNC_FLUSH broker take a long bootstrap time [rocketmq]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #7233: [Bug] SYNC_FLUSH broker take a long bootstrap time
URL: https://github.com/apache/rocketmq/issues/7233
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] SYNC_FLUSH broker take a long bootstrap time [rocketmq]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #7233:
URL: https://github.com/apache/rocketmq/issues/7233#issuecomment-2309060990
This issue was closed because it has been inactive for 3 days since being marked as stale.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] SYNC_FLUSH broker take a long bootstrap time [rocketmq]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #7233:
URL: https://github.com/apache/rocketmq/issues/7233#issuecomment-2305944892
This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org