-
Notifications
You must be signed in to change notification settings - Fork 648
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
Add option to account history plugin to keep operations that happened in last X blocks in memory #2648
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR for #2268.
Note: this triggers auto-replay.
Add 2 node startup options (available when the
account_history
plugin is enabled):min-blocks-to-keep
- Operations which are in the latestX
blocks will be kept in memory. This option only takes effect whentrack-account
is not used andmax-ops-per-account
is not zero. Note that this option may cause more history records to be kept in memory than the limit defined by themax-ops-per-account
option, but the amount will be limited by themax-ops-per-acc-by-min-blocks
option. The default value is30,000
blocks.max-ops-per-acc-by-min-blocks
- A potential higher limit on the maximum number of operations per account to be kept in memory when themin-blocks-to-keep
option causes the amount to exceed the limit defined by themax-ops-per-account
option. If this is less thanmax-ops-per-account
,max-ops-per-account
will be used. The default value is1,000
records.