distsqlrun: make txn mem mon own local flow's#26108
distsqlrun: make txn mem mon own local flow's#26108craig[bot] merged 1 commit intocockroachdb:masterfrom
Conversation
eeea274 to
bce546c
Compare
|
Review status: all files reviewed at latest revision, all discussions resolved, all commit checks successful. Comments from Reviewable |
|
Review status: all files reviewed at latest revision, all discussions resolved, all commit checks successful. pkg/sql/distsqlplan/aggregator_funcs_test.go, line 71 at r1 (raw file):
It's a bit confusing that you use pkg/sql/distsqlrun/server.go, line 406 at r1 (raw file):
nit: I would also call this Comments from Reviewable |
Previously, DistSQL flows that were local to the coordinator node used a memory monitor that was owned by a generic distsql memory monitor. This was misleading, as it prevented memory used by distsql local to a node from showing up in the query's used memory. Now, a query's transaction memory monitor is passed to the local distsql flow created for it. The remote distsql flows still are monitored by the generic distsql one, but this is a start at bettering the situation. Release note: None
bce546c to
5324674
Compare
|
Review status: 3 of 4 files reviewed at latest revision, 2 unresolved discussions, all commit checks successful. pkg/sql/distsqlplan/aggregator_funcs_test.go, line 71 at r1 (raw file): Previously, asubiotto (Alfonso Subiotto Marqués) wrote…
Yeah... but this is in a different package, so you can't use the unexported I'll add a comment to Comments from Reviewable |
|
bors r+ |
26108: distsqlrun: make txn mem mon own local flow's r=jordanlewis a=jordanlewis Previously, DistSQL flows that were local to the coordinator node used a memory monitor that was owned by a generic distsql memory monitor. This was misleading, as it prevented memory used by distsql local to a node from showing up in the query's used memory. Now, a query's transaction memory monitor is passed to the local distsql flow created for it. The remote distsql flows still are monitored by the generic distsql one, but this is a start at bettering the situation. Closes #25879. Release note: None Co-authored-by: Jordan Lewis <jordanthelewis@gmail.com>
Build succeeded |
Previously, DistSQL flows that were local to the coordinator node used a
memory monitor that was owned by a generic distsql memory monitor. This
was misleading, as it prevented memory used by distsql local to a node
from showing up in the query's used memory.
Now, a query's transaction memory monitor is passed to the local distsql
flow created for it. The remote distsql flows still are monitored by the
generic distsql one, but this is a start at bettering the situation.
Closes #25879.
Release note: None