What yugabyte/yugabyte-db shipped
Generated by FoxPlug from public activity — not affiliated with Yugabyte.
Week of September 14, 2026
What shipped
- Distributed trace context now propagates across RPC boundaries, with the request header carrying an optional trace-context field that flows from caller to callee. Pull request #33112
- The dist_trace library was reworked into a span-and-scope API with entry points for starting traces and re-establishing parent context. Pull request #33116
- Trace context now carries across thread boundaries so work handed to worker, reactor, scheduler, or Raft apply threads continues the originating trace. Pull request #33114
- Trace context propagates over the PG-tserver shared memory exchange so requests bypassing the RPC stack still join the caller's trace. Pull request #33113
- The traceparent header now propagates to PG backends via the startup packet so backend initialization and statements root under the originating trace. Pull request #33115
- Per-tablet in-memory aggregation was added for SST statistics to answer questions across multiple SSTfiles rather than single-file records. Pull request #33887
- Index backfill failures now report with PostgreSQL SQLSTATE codes instead of the generic XX000 error code. Pull request #33748
- CheckpointMultipleDatabases in xCluster replication was capped at 64 databases to prevent excessive concurrent DDL operations. Pull request #33933
- Python 3.14 was added to the supported interpreter versions for YBA with updated dependency pins. Pull request #33993
- YBA now fails fast with a clear error when the master leader is missing instead of silently dereferencing null values. Pull request #33840
Why it matters
Distributed tracing infrastructure across RPC boundaries and thread hops enables operators to track requests through the entire system. Improvements to error reporting, resource limits, and safety checks make the database more reliable and easier to debug.
Changelog entry
- Distributed trace context now propagates across RPC boundaries Pull request #33112
- Reworked dist_trace library into span-and-scope API Pull request #33116
- Trace context carries across thread boundaries Pull request #33114
- Trace context propagates over PG-tserver shared memory exchange Pull request #33113
- Traceparent propagates to PG backends via startup packet Pull request #33115
- Per-tablet in-memory aggregation for SST statistics Pull request #33887
- Index backfill failures report with PostgreSQL SQLSTATE codes Pull request #33748
- CheckpointMultipleDatabases capped at 64 databases in xCluster Pull request #33933
- Python 3.14 added to YBA supported versions Pull request #33993
- YBA fails fast with clear error when master leader is missing Pull request #33840
Distributed tracing now flows across RPC boundaries, thread hops, and shared memory exchanges. Better error codes and safety checks improve debugging and prevent silent failures.
This week's work strengthens distributed tracing throughout YugabyteDB. Trace context now propagates across RPC boundaries, thread boundaries, and the PG-tserver shared memory path—enabling operators to follow requests through the entire system. We also improved error reporting with proper PostgreSQL error codes, added resource limits for xCluster operations, and added safety checks to fail fast when critical components are missing.