-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
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
[BUG] apecloud-mysql smartengine:The parameter does not take effect after vscale #460
Comments
haowen159
changed the title
[BUG] The parameter does not take effect after vscale
[BUG] apecloud-mysql smartengine:The parameter does not take effect after vscale
Apr 22, 2024
The rerender feature needs to be enabled on the addon to take effect. I will update the addon. |
sophon-zt
added a commit
that referenced
this issue
Jul 19, 2024
sophon-zt
added a commit
that referenced
this issue
Jul 19, 2024
sophon-zt
added a commit
that referenced
this issue
Jul 19, 2024
sophon-zt
added a commit
that referenced
this issue
Jul 19, 2024
sophon-zt
added a commit
that referenced
this issue
Jul 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
在apecloud-mysql引擎下测试内存扩容,发现相应的参数没有受到影响。
测试流程:
1.根据配置文件,测试loose_smartengine_db_write_buffer_size有没有发生变化,渲染后,它为smartengine_db_write_buffer_size
2.在测试程序中,创建了apecloud-mysql并开启smartengine配置的集群:smarte-mpkiua ,初始内存为1G,获取相应的loose_smartengine_db_write_buffer_size值,将其扩容到1.5G后,再获取该值进行对比,发现扩容前后该值没有变化
3.为了验证结果,我手动创建了内存为1G和1.5G,其余配置与测试集群相同的两个集群ape-1和ape-2,获取该值后发现它受memory大小影响
4.随后我又检查了测试集群的内存大小,并手动获取该值,发现确实存在问题:测试集群扩容成功,该值没有变化
The text was updated successfully, but these errors were encountered: