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
153740: kvserver/rangefeed: add capacity to node level buffered sender r=stevendanna a=wenyihu6
Resolves: #152505
Release note: none
---
**kvserver/rangefeed: add capacity to node level buffered sender**
This patch adds capacity to node level buffered sender which will shut down all
registrations if the node level buffer had overflowed.
Part of: #129813
Release note: none
---
**kvserver/rangefeed: rename overflow to overflowed**
This commit renames overflow to overflowed in BufferedSender for clarity.
---
**kvserver/rangefeed: dynamically adjust capacity per buffered sender**
Previously, buffered sender capacity was configured via a cluster setting. This
commit removes that setting and makes capacity scale dynamically with the number
of active registrations. The minimum (and default) is 4096 * 20, and capacity
never drops below that. Above the minimum, it grows as 4096 * <active
registrations>. Events already buffered will not dropped when capacity
decreases, and capacity is not adjusted during shutdown (0).
---
**rangefeed: move back to static (bug configurable) send queue limit**
The interactions here probably require more thought before doing
anything more complicated than a simple static limit.
Epic: none
Release note: None
---
**rangefeed: fix incorrect comment**
Epic: none
Release note: None
---
**rangefeed: deflake TestUnbufferedRegWithStreamManager**
Under stress, this test would fail because attempting to publish 20
events in a tight loop would overwhelm the processor's event buffer
(which has a capacity of 16).
Epic: none
Release note: None
153965: sql/inspect: support checking multiple indexes in one INSPECT job r=spilchen a=spilchen
Previously, there was an assert that made sure when building the INSPECT job that we only had one check. This removes that assert so that we can have mulitple checks. When you run INSPECT against many indexes on a table or against a database, we will have multiple checks, so it was necessary for that case.
Closes#148300
Release note: none
Epic: none
154027: activity: add fallback isolation level for statements not in transaction r=jasonlmfong a=jasonlmfong
The change is achieved by retrieving the session default isolation level
closes: [#153931](#153931)
Epic: None
Release note: None
Co-authored-by: wenyihu6 <[email protected]>
Co-authored-by: Steven Danna <[email protected]>
Co-authored-by: Matt Spilchen <[email protected]>
Co-authored-by: Jason Fong <[email protected]>
0 commit comments