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.

Sign up for GitHub

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

Jump to bottom

Dataserver expansion or node change causes data migration process to increase memory #52

Closed

Synex-wh opened this issue Sep 19, 2019 · 0 comments

Labels

bug

Contributor

Synex-wh commented Sep 19, 2019

Describe the bug

All nodes on the dataserver are pressured to measure the maximum amount of storage. After the data is expanded, the new node immediately finds frequent fgc.
On the remaining machines after the same amount of data has been relocated, there are no more fgc occurrences than the new node.

Analytical solution

dump memory to see the new node's string type object is significantly more than the original node, and basically expands about 10 times, the main object of the resident old is the string takes up a larger
All previous access data including synchronous and backup data will perform the same character caching function for pub, but the data relocation at the initial stage of capacity expansion is not processed, and the processing problem is solved.

Synex-wh added the bug label

dzdx closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment