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
154670: log: finalize structured event logging channel migration r=jasonlmfong a=jasonlmfong
The following structured events should have their logging channels migrated:
CreateChangefeed: TELEMETRY -> CHANGEFEED
AlterChangefeed: TELEMETRY -> CHANGEFEED
ChangefeedFailed: TELEMETRY -> CHANGEFEED
ChangefeedCanceled: TELEMETRY -> CHANGEFEED
ChangefeedEmittedBytes: TELEMETRY -> CHANGEFEED
SampledQuery: TELEMETRY -> SQL_EXEC
SampledTransaction: TELEMETRY -> SQL_EXEC
SlowQuery: SQL_PERF -> SQL_EXEC
LargeRow: SQL_PERF -> SQL_EXEC
TxnRowsWrittenLimit: SQL_PERF -> SQL_EXEC
TxnRowsReadLimit: SQL_PERF -> SQL_EXEC
SlowQueryInternal: SQL_INTERNAL_PERF -> SQL_EXEC
LargeRowInternal: SQL_INTERNAL_PERF -> SQL_EXEC
TxnRowsWrittenLimitInternal: SQL_INTERNAL_PERF -> SQL_EXEC
TxnRowsReadLimitInternal: SQL_INTERNAL_PERF -> SQL_EXEC
This is achieved by setting default of `log.channel_compatibility_mode.enabled` to false
This change also updates the protobuff documentation
Epic: CRDB-53410
Release note (ops change): This change completes the migration of changfeed events, sample query/txn events, sql_perf events into their respective new logging channels. In order to keep using the old channels, users have to set the setting:
`log.channel_compatibility_mode.enabled` to true.
----
log: fix missing logs for internal events
previously the logs were only flowing for the non-internal events
Epic: None
Release note (bug fix): Previously, CockroachDB would not log events for
TxnRowsRead and TxnRowsWritten guardrail for internal queries into
SQL_INTERNAL_PERF channel. The bug has been present since 21.2 and
has now been fixed.
Co-authored-by: Jason Fong <[email protected]>
Copy file name to clipboardExpand all lines: docs/generated/settings/settings-for-tenants.txt
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,7 @@ kv.transaction.write_pipelining.locking_reads.enabled boolean true if enabled, t
108
108
kv.transaction.write_pipelining.ranged_writes.enabled boolean true if enabled, transactional ranged writes are pipelined through Raft consensus application
109
109
kv.transaction.write_pipelining.enabled (alias: kv.transaction.write_pipelining_enabled) boolean true if enabled, transactional writes are pipelined through Raft consensus application
110
110
kv.transaction.write_pipelining.max_batch_size (alias: kv.transaction.write_pipelining_max_batch_size) integer 128 if non-zero, defines that maximum size batch that will be pipelined through Raft consensus application
111
-
log.channel_compatibility_mode.enabled boolean true when true, logs will continue to log to the expected logging channels; when false, logs will be moved to new logging channels as part of a logging channel consolidation effort application
111
+
log.channel_compatibility_mode.enabled boolean false when true, logs will to log to their legacy (pre 26.1) logging channels; when false, logs will be logged to new logging channels application
112
112
obs.tablemetadata.automatic_updates.enabled boolean false enables automatic updates of the table metadata cache system.table_metadata application
113
113
obs.tablemetadata.data_valid_duration duration 20m0s the duration for which the data in system.table_metadata is considered valid application
114
114
schedules.backup.gc_protection.enabled boolean true enable chaining of GC protection across backups run as part of a schedule application
Copy file name to clipboardExpand all lines: docs/generated/settings/settings.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -139,7 +139,7 @@
139
139
<tr><td><divid="setting-kv-transaction-write-pipelining-max-batch-size" class="anchored"><code>kv.transaction.write_pipelining.max_batch_size<br/>(alias: kv.transaction.write_pipelining_max_batch_size)</code></div></td><td>integer</td><td><code>128</code></td><td>if non-zero, defines that maximum size batch that will be pipelined through Raft consensus</td><td>Basic/Standard/Advanced/Self-Hosted</td></tr>
140
140
<tr><td><divid="setting-kvadmission-store-provisioned-bandwidth" class="anchored"><code>kvadmission.store.provisioned_bandwidth</code></div></td><td>byte size</td><td><code>0 B</code></td><td>if set to a non-zero value, this is used as the provisioned bandwidth (in bytes/s), for each store. It can be overridden on a per-store basis using the --store flag. Note that setting the provisioned bandwidth to a positive value may enable disk bandwidth based admission control, since admission.disk_bandwidth_tokens.elastic.enabled defaults to true</td><td>Advanced/Self-Hosted</td></tr>
141
141
<tr><td><divid="setting-kvadmission-store-snapshot-ingest-bandwidth-control-enabled" class="anchored"><code>kvadmission.store.snapshot_ingest_bandwidth_control.enabled</code></div></td><td>boolean</td><td><code>true</code></td><td>if set to true, snapshot ingests will be subject to disk write control in AC</td><td>Advanced/Self-Hosted</td></tr>
142
-
<tr><td><divid="setting-log-channel-compatibility-mode-enabled" class="anchored"><code>log.channel_compatibility_mode.enabled</code></div></td><td>boolean</td><td><code>true</code></td><td>when true, logs will continue to log to the expected logging channels; when false, logs will be moved to new logging channels as part of a logging channel consolidation effort</td><td>Basic/Standard/Advanced/Self-Hosted</td></tr>
142
+
<tr><td><divid="setting-log-channel-compatibility-mode-enabled" class="anchored"><code>log.channel_compatibility_mode.enabled</code></div></td><td>boolean</td><td><code>false</code></td><td>when true, logs will to log to their legacy (pre 26.1) logging channels; when false, logs will be logged to new logging channels</td><td>Basic/Standard/Advanced/Self-Hosted</td></tr>
143
143
<tr><td><divid="setting-obs-tablemetadata-automatic-updates-enabled" class="anchored"><code>obs.tablemetadata.automatic_updates.enabled</code></div></td><td>boolean</td><td><code>false</code></td><td>enables automatic updates of the table metadata cache system.table_metadata</td><td>Basic/Standard/Advanced/Self-Hosted</td></tr>
144
144
<tr><td><divid="setting-obs-tablemetadata-data-valid-duration" class="anchored"><code>obs.tablemetadata.data_valid_duration</code></div></td><td>duration</td><td><code>20m0s</code></td><td>the duration for which the data in system.table_metadata is considered valid</td><td>Basic/Standard/Advanced/Self-Hosted</td></tr>
145
145
<tr><td><divid="setting-schedules-backup-gc-protection-enabled" class="anchored"><code>schedules.backup.gc_protection.enabled</code></div></td><td>boolean</td><td><code>true</code></td><td>enable chaining of GC protection across backups run as part of a schedule</td><td>Basic/Standard/Advanced/Self-Hosted</td></tr>
0 commit comments