Summary
In Oct 3, Cosmoshub Lava provider's QOS availability score dropped so much

And many provider's cosmos node met oom issue. (can check in discord incentivized-cosmos-hub channel)
I have checked the log when the cosmos node ram continuesly increased.
/cosmos/tx/v1beta1/txs?query=tx.height%3E%3D22022712&query=tx.height%3C%3D22022752&pagination.limit=100&pagination.offset=0 was the query which caused the OOM issue
Is it possible to limit this kind of query?
Problem Definition
/cosmos/tx/v1beta1/txs?query=tx.height%3E%3D22022712&query=tx.height%3C%3D22022752&pagination.limit=100&pagination.offset=0 this kind of api query can cause cosmos node memory leak.
Proposed Feature
Limit the query like /cosmos/tx/v1beta1/txs?query=tx.height%3E%3D22022712&query=tx.height%3C%3D22022752&pagination.limit=100&pagination.offset=0 on cosmos chains apis
Summary
In Oct 3, Cosmoshub Lava provider's QOS availability score dropped so much

And many provider's cosmos node met oom issue. (can check in discord incentivized-cosmos-hub channel)
I have checked the log when the cosmos node ram continuesly increased.
/cosmos/tx/v1beta1/txs?query=tx.height%3E%3D22022712&query=tx.height%3C%3D22022752&pagination.limit=100&pagination.offset=0was the query which caused the OOM issueIs it possible to limit this kind of query?
Problem Definition
/cosmos/tx/v1beta1/txs?query=tx.height%3E%3D22022712&query=tx.height%3C%3D22022752&pagination.limit=100&pagination.offset=0this kind of api query can cause cosmos node memory leak.Proposed Feature
Limit the query like
/cosmos/tx/v1beta1/txs?query=tx.height%3E%3D22022712&query=tx.height%3C%3D22022752&pagination.limit=100&pagination.offset=0on cosmos chains apis