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
150725: pcr: reorder time series dashboards r=alicia-l2 a=alicia-l2
Swapped order of Replication Lag and Logical Bytes graphs in Physical Cluster Replication DB Console
Fixes: #147621
Release note: none
151548: roachtest: fix overlapping failure injection bug r=Dev-Kyle a=Dev-Kyle
This change fixes a bug regarding failure injections overlapping over each other when not intended. Marks the mutator step itself to also set unavailableNodes so sequential failure injections don't insert into them. Also considers `waitForStableClusterVersionStep` as incompatible when injecting a network partition recovery.
Epic: none
Release note: none
Fixes: #151522 , #151384
151559: kvcoord: fix txnWriteBuffer for batches with limits and Dels r=yuzefovich a=yuzefovich
Previously, the txnWriteBuffer was oblivious to the fact that some transformed requests might be returned incomplete due to limits set on the BatchRequest (either TargetBytes or MaxSpanRequestKeys), so it would incorrectly think that it has acquired locks on some keys when it hasn't. Usage from SQL was only exposed to the bug via special delete-range fast-path where we used point Dels (i.e. a stmt of the form `DELETE FROM t WHERE k IN (<ids>)` where there are gaps between `id`s) since it always sets a key limit of 600. This commit fixes this particular issue for Dels transformed into Gets and adds a couple of assertions that we don't see batches with CPuts and/or Puts with the limits set.
Additionally, it adjusts the comment to indicate which requests are allowed in batches with limits.
Given that this feature is disabled by default and in the private preview AND it's limited to the DELETE fast-path when more than 600 keys are deleted, I decided to omit the release note.
Fixes: #151294.
Fixes: #151649.
Release note: None
151692: log: add KV_EXEC and CHANGEFEED logging channels r=kyle-a-wong a=kyle-a-wong
KV_EXEC is intended to contain KV events that don't fall into the KV_DISTRIBUTION channel
CHANGEFEED is for changefeed events that are currently being logged to the TELEMETRY channel
Part of: CRDB-53411
Epic: CRDB-53410
Release note (ops change): Introduces two new logging channels: KV_EXEC and CHANGEFEED. KV_EXEC will contain kv events that don't fall into the KV_DISTRIBUTION channel and CHANGEFEED will eventually contain changefeed events (This change doesn't add any logic to move existing changefeed logs to this channel).
151750: roachtest: update pgjdbc test for new portal behavior r=rafiss a=rafiss
We recently merged #151153 which makes certain statements invalid when used in a pausable portal. This causes a few PGJDBC tests to fail during the test setup phase.
fixes#151582
Release note: None
151752: roachtest: deflake hibernate timeouts r=rafiss a=rafiss
This patch increases the timeout to avoid hitting spurious failures when the test takes too long.
fixes#151591fixes#151711
Release note: None
151753: sctestbackupccl: deflake schemachanger tests during BACKUP r=rafiss a=rafiss
Increase the timeout for waiting for a schema change to complete, which can take a longer time if there are concurrent backups.
fixes#151469fixes#150842
Release note: None
Co-authored-by: Alicia Lu <[email protected]>
Co-authored-by: Kyle <[email protected]>
Co-authored-by: Yahor Yuzefovich <[email protected]>
Co-authored-by: Kyle Wong <[email protected]>
Co-authored-by: Rafi Shamim <[email protected]>
0 commit comments