-
Notifications
You must be signed in to change notification settings - Fork 359
fix: limit the max tx results #2751
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
base: main
Are you sure you want to change the base?
Conversation
rach-id
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| return &TxIndexConfig{ | ||
| Indexer: "kv", | ||
| Indexer: "kv", | ||
| MaxSearchResults: 10000, // Default to 10000, matching DefaultMaxSearchResults in kv package |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not use the constant directly?
| // Use configured max search results, or default if not set (0) | ||
| maxResults := cfg.TxIndex.MaxSearchResults | ||
| if maxResults == 0 { | ||
| maxResults = 10000 // DefaultMaxSearchResults from kv package |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same
|
Converting to draft b/c QuickNode still experienced OOMs even after disabling the endpoints that allow tx searches. They stop experiencing OOMs after disabling the indexer. |
Motivation
https://celestia-team.slack.com/archives/C07TJQPUDJP/p1767923097339989