transparency-dev / transparency-dev/tesseract
antispam_mem_table_size and antispam_base_table_size cannot be lowerd once initialized
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 37
- Forks
- 18
- Avg merge
- 19h 22m
- Merged PRs (30d)
- 15
Description
Description
antispam_mem_table_size & antispam_base_table_size control the max size of Badger table (or max size of individual .sst files). Once these parameters are initialzed, lowering them can cause POSIX process to fail and remain stuck, typically with an error similar to: “Arena too small, toWrite:40 newTotal:174483044 limit:174483027”.
For now, a note should be added to document the bebavoir.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the documentation for antispam_mem_table_size and antispam_base_table_size, which control Badger table and .sst file sizes. Add a note explaining that lowering either parameter after initialization can cause the POSIX process to fail and remain stuck, including the reported “Arena too small” behavior, then check that the warning is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100