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
Active Statements: doesn't show internal queries at all or internal app filter
Active Transaction: show internal transactions and the app filter have each internal app as an item
Sessions: doesn't show internal apps by default and have a filter with all internal app names grouped in a single "$internal"
Since those 3 tabs are related to Active Executions and they all use the same source of data they should be compatible, so the Active Statement and Transactions should be updated to have the same behaviour as Sessions:
Under the App filter show a single $internal that show/hide all internal statement/transactions
Don't show internal by default, but if that filter is select, those executions are displayed
83014: ui: add internal app filter to active statements and transactions pages r=ericharmeling a=ericharmeling
This PR adds a single internal app filter option on to the Active Statements and Active Transactions pages. Active
statements and transactions run by internal apps are no longer displayed by default.
See commit message for release note.
https://user-images.githubusercontent.com/27286675/174156635-39d8649a-df91-4550-adb5-b3c167d54ed5.movFixes#81072.
83707: roachtest: run workload from the tenant node r=knz a=stevendanna
The secure URL refers to paths on disk on the clusters in the
node. Since we only create the tenant-scoped certs on the tenant node,
we need to run workload from that node.
Fixes#82266
Depends on #83703
Release note: None
84003: storage: close pebble iter gracefully when NewPebbleSSTIterator fails r=erikgrinaker a=msbutler
Currently, if `pebble.NewExternalIter` sets pebbleIterator.inuse to True, but
then fails, the subsequent `pebbleIterator.destroy()` will panic unecessarily,
since the caller of `pebble.NewExternalIter` is not actually using the iter.
This bug causes TestBackupRestoreChecksum to flake in #83984.
To fix, this patch uses pebble.Close() to gracefully close the pebbleIterator
if `pebble.NewExternalIter` fails.
Release Note: None
84039: prometheus: use older node_exporter r=nicktrav a=tbg
v1.3.1, the most up to date released version, has a bug that inflates
the bytes written by ~8x for NVMe drives (which in particular includes
the default drives for our GCE roachprod machines). Fundamentally this
is caused by the fact that these devices use a 4K sector size whereas
the kernel will always report based on a 512B sector size.
This took us a while to figure out, and to avoid repeating this exercise
periodically, downgrade node_exporter to 1.2.2, which pre-dates a
refactor that introduces the regression.
See: prometheus/node_exporter#2310
Release note: None
Co-authored-by: Eric Harmeling <[email protected]>
Co-authored-by: Steven Danna <[email protected]>
Co-authored-by: Michael Butler <[email protected]>
Co-authored-by: Tobias Grieger <[email protected]>
Right now we have
Since those 3 tabs are related to Active Executions and they all use the same source of data they should be compatible, so the Active Statement and Transactions should be updated to have the same behaviour as Sessions:
$internal
that show/hide all internal statement/transactionsJira issue: CRDB-15366
The text was updated successfully, but these errors were encountered: