feat: support custom variables_hash_max_size parameters in config.yaml #4344
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.
What this PR does / why we need it:
Signed-off-by: Firstsawyou yuelinz99@gmail.com
When apisix is in
make run, it will prompt the following warning message:$ make run ./bin/apisix start /usr/local/openresty/luajit/bin/luajit ./apisix/cli/apisix.lua start nginx: [warn] could not build optimal variables_hash, you should increase either variables_hash_max_size: 1024 or variables_hash_bucket_size: 64; ignoring variables_hash_bucket_sizeTherefore, this PR will add the
variables_hash_max_sizeparameter to solve the above warning problem.Since the value of
variables_hash_max_size: 1024is not enough, setvariables_hash_max_size: 2048Pre-submission checklist: