Document behavior of antispam_mem_table_size and antispam_base_table_…#880
Open
jiemingwang wants to merge 1 commit into
Open
Document behavior of antispam_mem_table_size and antispam_base_table_…#880jiemingwang wants to merge 1 commit into
jiemingwang wants to merge 1 commit into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
jiemingwang
force-pushed
the
antispam_mem_table_size
branch
from
b5533b4 to
5a7b877
Compare
This file contains hidden or 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
1 participant
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.
Document behavior of antispam_mem_table_size & antispam_base_table_size.
These parameters must not be reduced after initial configuration (defaults are antispam_mem_table_size=256<<20 and antispam_base_table_size=16<<20). Lowering them will cause the POSIX process to fail during BadgerDB initialization and remain stuck, typically with an error similar to: “Arena too small, toWrite:40 newTotal:174483044 limit:174483027”.