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
changefeedccl: emit warning when resolved or min_checkpoint_frequency is set too low
This change adds client-side notices to `CREATE CHANGEFEED` and `ALTER CHANGEFEED` statements
when the `resolved` or `min_checkpoint_frequency` options are set below a recommended threshold
(e.g., 500ms). These warnings aim to guide users toward more balanced configurations.
Setting these options too low can significantly increase CPU usage due to more frequent
checkpointing and resolved timestamp emissions, introducing performance trade-offs.
Epic: CRDB-52074Fixes#149238
Release note (general change): A warning is now emitted when creating or altering a
changefeed with `resolved` or `min_checkpoint_frequency` set below 500ms. This helps
users understand the tradeoff between message latency and cluster CPU usage.
testFeed:=feed(t, f, `CREATE CHANGEFEED FOR ☃ INTO 'kafka://does.not.matter/' WITH resolved='20ms'`)
5110
+
testFeed:=feed(t, f, `CREATE CHANGEFEED FOR ☃ INTO 'kafka://does.not.matter/' WITH resolved='5s'`)
5107
5111
defercloseFeed(t, testFeed)
5108
-
// Note: default min_checkpoint_frequency is set to 100ms in startTestCluster.
5109
-
require.Equal(t, `resolved (20ms) messages will not be emitted more frequently than the default min_checkpoint_frequency (100ms), but may be emitted less frequently`, actual)
5112
+
require.Equal(t, `resolved (5s) messages will not be emitted more frequently than the default min_checkpoint_frequency (30s), but may be emitted less frequently`, actual)
0 commit comments