-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kv: Add created
column to active_range_feeds
table.
#77597
Conversation
StartTS: startFrom, | ||
Span: span, | ||
StartTS: startFrom, | ||
EstablishedTime: timeutil.Now(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what exactly we want the semantics of this field to be, but maybe we should set it whenever the rangefeed is actually established, i.e. when we get a nil
error back from client.RangeFeed()
? At least to me, "established" implies that the rangefeed connection was successfully set up. I guess that also implies that it would get updated if we ever disconnect or reconnect too.
Alternatively, we could consider calling this Created
and use Established
as a separate field.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack... I was going back and forth w/ established v created. Changing to created.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but remember to update commit/PR description.
established
column to active_range_feeds
table.created
column to active_range_feeds
table.
Add `created` column to `active_range_feeds` table. This column is initialized to the time when the partial range feed was created. This allows us to determine, among other things, whether or not the rangefeed is currently performing a catchup scan (i.e. it's resolved column is 0), and how long the scan has been running for. Release Notes (enterprise): Add created time column to `crdb_internal.active_range_feeds` virtual table to improve observability and debugability of rangefeed system. Release Justification: Low impact observability/debugability improvement.
bors r+ |
Build succeeded: |
Add
created
column toactive_range_feeds
table.This column is initialized to the time when the partial range feed
was created. This allows us to determine, among other things,
whether or not the rangefeed is currently performing a catchup scan
(i.e. it's resolved column is 0), and how long the scan has been running
for.
Release Notes (enterprise): Add created time column
to
crdb_internal.active_range_feeds
virtual table to improve observabilityand debugability of rangefeed system.
Fixes #77581
Release Justification: Low impact observability/debugability improvement.