GenerousMan opened a new issue, #7013:
URL: https://github.com/apache/rocketmq/issues/7013

   ### 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
   
   Mac, M1
   
   ### RocketMQ version
   
   latest
   
   ### JDK Version
   
   _No response_
   
   ### Describe the Bug
   
   Regardless of whether the cold read control switch is turned on, 
initPageSize() will be executed. However in some cases it may trigger an error.
   
   ### Steps to Reproduce
   
   turn off the related switch: 
   coldDataScanEnable                                =  false
   coldDataFlowControlEnable                    =  false
   
   then start the broker, there will still be such log in store.log: 
   2023-07-03 13:54:01 INFO main - initPageSize pageSize: 4096
   
   However, this discussion shows that in some cases, it will lead to an error:
   https://github.com/apache/rocketmq/discussions/7007
   
   ### What Did You Expect to See?
   
   The initialization should only be triggered after the switch is turned on.
   
   ### What Did You See Instead?
   
   then start the broker, there is such log in store.log: 
   2023-07-03 13:54:01 INFO main - initPageSize pageSize: 4096
   
   ### 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to