You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
158341: distmerge: add merge processor scaffolding r=mw5h a=mw5h
#### bulkmerge: add processors and DistSQL physical planning
This commit introduces the initial implementation of bulkmerge processors
for distributed merge operations. It adds three new processor types:
MergeLoopback, BulkMerge, and MergeCoordinator, along with the DistSQL
physical planning infrastructure to orchestrate them.
The MergeLoopback processor runs on the coordinator node and generates
initial tasks. The BulkMerge processors run on each SQL instance to
perform merge operations. The MergeCoordinator collects results from
all merge processors.
This commit also updates the vectorized execution engine (execplan.go)
to recognize the new processor cores, preventing panics when these
processors are encountered.
Informs #156580
Release note: None
#### backup: deduplicate routing logic with physicalplan package
Previously, the backup package contained duplicate implementations of
routingDatumsForSQLInstance and routingSpanForSQLInstance that were
identical to functions recently added to pkg/sql/physicalplan. This
commit removes these duplicates and uses the shared implementations:
RoutingDatumsForSQLInstance and MakeInstanceRouter.
This reduces code duplication and ensures consistent routing behavior
across DistSQL physical planning for both backup/restore and bulk merge
operations.
Informs #156580
Release note: None
#### physicalplan: set DefaultDest to nil to catch routing bugs
Changes MakeInstanceRouter to set DefaultDest to nil instead of stream 0.
When DefaultDest is nil, any routing key that doesn't match a span will
produce an error rather than silently routing to an arbitrary stream.
This helps catch coordination bugs early.
Updates merge_loopback.go to generate a routing key for its SQL instance
using physicalplan.RoutingDatumsForSQLInstance instead of a hardcoded
"loopback" key. This ensures the routing key matches one of the spans in
the router rather than relying on the DefaultDest fallback.
The test expectation is updated from "loopback->merge->coordinator" to
"node1->merge->coordinator" to reflect the explicit routing behavior.
Fixes#156580
Release note: None
158596: kvnemesis: correctly verify the span config of the system range r=miraradeva a=miraradeva
Previously, kvnemesis verified the correct span config for some critical ranges: meta (r1), liveness (r2) and system (r3). However, as of 8844739, meta1 and meta2 start off as separate ranges, pushing the system range to r4. It's important for this range to be replicated correctly in kvnemesis to ensure it's available in the presence of network partitions. Unavailability of the system range can result in splits not able to allocate new range IDs.
This commit bumps up the max range ID used for span config verification from 3 to 4.
Informs: #158366
Release note: None
158606: mma: always incorporate RangeMsg.RangeLoad r=wenyihu6 a=sumeerbhola
Epic: CRDB-55052
Release note: None
158610: mma: tweak the comment of MakeStoreLoadMsg r=wenyihu6 a=sumeerbhola
This is mainly to clarify that we sum the load and capacity reported per store inside MMA, so tweaking the capacity calculation approach may not be possible in isolation.
Epic: CRDB-55052
Release note: None
Co-authored-by: Jeff Swenson <[email protected]>
Co-authored-by: Matt White <[email protected]>
Co-authored-by: Mira Radeva <[email protected]>
Co-authored-by: sumeerbhola <[email protected]>
0 commit comments