Skip to content
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

Control logging of state #102

Open
martinsumner opened this issue Dec 3, 2021 · 2 comments
Open

Control logging of state #102

martinsumner opened this issue Dec 3, 2021 · 2 comments

Comments

@martinsumner
Copy link
Owner

Use format_status/2 in gen_server so as not to log large amounts of state in crash dumps

@martinsumner
Copy link
Owner Author

Related to this is the problem of the change_queue in the aae_keystore.

This queue builds up all puts seen since the rebuild of the aae_keystore was started. This can end up being very large, if there are a lot of PUTs happening concurrently to the rebuild. There is also the possibility that rebuilds could be occurring concurrently on a node.

The queue could cause a node to run out of memory, and there is no way to maintain the functional integrity of the store if the queue is limited.

Preference is therefore to switch to using disk_log for this queue. This will be slower, but means there is no risk with memory exhaustion during the rebuild.

@martinsumner
Copy link
Owner Author

#103

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant