-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
76266: pprofui: Increase concurrency for profiles r=dhartunian a=rimadeodhar In this PR, we increase the concurrency limit while running performance profiles (e.g. heap, CPU) from the Advanced Debug page within DB Console. Previously, attempting to run performance profiling in parallel for the same node would result in race condition causing one of the profiles to overwrite the other. This would cause "Profile not found: profile may have expired" errors. The occurrence of these errors was exacerbated by the new feature enabling running profiles on any nodes as it increased the likelihood of race conditions for profiles being run on a node at the same time. By allowing atleast two profile runs at the same time decreases the likelihood of one request overwriting the other. This does not completely eliminate the problem but will reduce the frequency of occurrence. This PR also updates the error message returned when a profile is not found to provide more details on the potential causes and remediation steps. Release note: None 76583: changefeedccl: allow users to alter changefeed options r=sherman-grewal a=sherman-grewal changefeedccl: allow users to alter changefeed options with the ALTER CHANGEFEED statement References #75895 Currently, with the ALTER CHANGEFEED statement users can only add or drop targets from an existing changefeed. In this PR, we would like to extend this functionality so that an user can edit and unset the options of an existing changefeed as well. The syntax of this addition is the following: ALTER CHANGEFEED <job_id> SET \<options\> UNSET <opt_list> Note that the <options> must follow the same syntax that is used when creating a changefeed with options. In particular, if you would like to set an option that requires a value, you must write SET opt = 'value' On the other hand, if you would like to set an option that requires no value, you must write SET opt Furthermore, this PR allows users to unset options. This can be achieved by writing UNSET <opt_list> Where <opt_list> is a list of options that you would like to unset. For example, if we would like to unset the diff and resolved options for changefeed 123, we would achieve this by writing ALTER CHANGEFEED 123 UNSET diff, resolved Release note (enterprise change): Added support to the ALTER CHANGEFEED statement so that users can edit and unset the options of an existing changefeed. The syntax of this addition is the following: ALTER CHANGEFEED <job_id> SET \<options\> UNSET <opt_list> Co-authored-by: rimadeodhar <[email protected]> Co-authored-by: Sherman Grewal <[email protected]>
- Loading branch information
Showing
15 changed files
with
781 additions
and
302 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.