We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug 当对pulsar引擎下集群的bookies组件的内存进行扩容后,参数dbStorage_writeCacheMaxSizeMb没有发生变化 To Reproduce 1.查阅pulsar的bookies配置文件发现,dbStorage_writeCacheMaxSizeMb受组件内存的影响。 2.使用测试程序创建puslar集群,并对bookies进行扩容,查询对比扩容前后的dbStorage_writeCacheMaxSizeMb值发现没有变化 扩容前配置: 扩容后配置: 结果: 3.为了验证测试结果,我又分别创建了和程序中配置相同的两个集群,并查询其与原集群的dbStorage_writeCacheMaxSizeMb值,发现dbStorage_writeCacheMaxSizeMb受memory大小影响,但是原集群没有变化
The text was updated successfully, but these errors were encountered:
JashBook
Successfully merging a pull request may close this issue.
Describe the bug
当对pulsar引擎下集群的bookies组件的内存进行扩容后,参数dbStorage_writeCacheMaxSizeMb没有发生变化
To Reproduce
1.查阅pulsar的bookies配置文件发现,dbStorage_writeCacheMaxSizeMb受组件内存的影响。
2.使用测试程序创建puslar集群,并对bookies进行扩容,查询对比扩容前后的dbStorage_writeCacheMaxSizeMb值发现没有变化
扩容前配置:
扩容后配置:
结果:
3.为了验证测试结果,我又分别创建了和程序中配置相同的两个集群,并查询其与原集群的dbStorage_writeCacheMaxSizeMb值,发现dbStorage_writeCacheMaxSizeMb受memory大小影响,但是原集群没有变化
The text was updated successfully, but these errors were encountered: