Open Azhng opened 2 years ago
NB: any new accounting here should be careful to ensure the bytes are released if the result is pushed to a HTTP client instead of being consumed locally.
We have marked this issue as stale because it has been inactive for 18 months. If this issue is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 10 days to keep the issue queue tidy. Thank you for your contribution to CockroachDB!
Currently, the memory accounting for txn contention event happens in the virtual table handler. This happens after the RPC result has been allocated. This is bad since the memory monitor does not have the opportunity to deny the allocation if the limit has been exceeded.
We should incrementally call
.Grow()
as we receive RPC response back fromiterate{Nodes, Pods}
Jira issue: CRDB-15948