-
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.
90451: Roachtest SSH Retries r=smg260 a=smg260 roachtest: This change introduces a default retry when encountering an error of `255` (SSH). It is transparent to callers. If desired, it would be relatively simple to expose this via the `cluster` interface and allow callers to specify a retry handler/options on a per command basis, perhaps something like: ``` // retry if we get an exit code of 12 retryOpts { opt: retry.Options { .. } , shouldRetryFn: func(res RunResultDetails) bool { return res.RemoteExitStatus == 12 } } c.RunE(ctx, nodes, retryOpts, "my_cmd") ``` but this PR does not introduce that. Today there appears the concept of a "roachprod" and a "command error", the former of which denotes an issue in roachprod handling code, the latter representing an error executing a command over SSH. This PR preserves this behaviour and introduces an updated function signature from `f(i int) ([]byte, error)` to `f(i int) RunResultDetails, error`. `RunResultDetails` has been expanded to capture information about the execution of a command, such as `stderr/our, exit code, error, attempt number`. Any roachprod error will result in an `error` being returned, and set in `RunResultDetails.Err`. Any command error would be only set in `RunResultDetails.Err` with the returned error being nil. This allows callers to differentiate between a roachprod and a command error - something which existing code depends on. Retry handling code can use a function's returned `RunResultDetails` to determine whether a retry should take place. This PR has default retry handling on `RunResultDetails.RemoteExitStatus == 255`. Notable changes - Retry on `255` exit code for any function executed via `ParallelE` - Consolidated `Run/RunWithDetails` (significant duplication of code) - Classify exit error at the session.go level so that it is available for all commands and to all callers - Remove `"echo $?"` option to print exit code at end of cmd. It is not clear why this was done. (Perhaps for visibility in logs?) Accompanying function to parse out the status has also been removed. The exit code is still accessible via the `RunResultDetails` - Update roachtests to check for SSH marker error instead of checking for `!install.NonZeroExitCode` Resolves: #73542 Release note: None Epic: [CRDB-21386](https://cockroachlabs.atlassian.net/browse/CRDB-21386) 91765: utilccl: fix a comment r=andreimatei a=andreimatei It was missing a key subject. Release note: None Epic: None 91884: changfeedccl: deflake TestAlterChangefeedTelemetry r=stevendanna a=stevendanna The job system clears the lease asyncronously after cancelation. This lease clearing transaction can cause a restart in the alter changefeed transaction, which will lead to different feature counter counts. Thus, we want to wait for the lease clear. However, the lease clear isn't guaranteed to happen, so we only wait a few seconds for it. Epic: None Release note: None 91885: roachpb, server, ui: add fingerprint ID to details pages r=maryliag a=maryliag **Commit 1** ui: use format from cluster-ui The format.js file was duplicated on db console, making it hard to maintain. This commit replaces all usages of the format functions on db-console package, to the ones from cluster-ui. Epic: None Release note: None **Commit 2** ui: add leading zeros to hex value with less than 16 chars Previously, some fingerprint IDs in hex format would have a leading 0, that was not being returning from the DB calls. This was causing confusion when seeing the value on the UI and trying to find the same fingerprint on our tables. This commits checks the hex values used and add the missing leading zeros back. Part Of: #91763 Release note (bug fix): Add leading zeros to fingerprint IDs with less than 16 characters. **Commit 3** roachpb, server, ui: add fingerprint ID to details pages Previously, there was no easy way to get a statement or fingerprint id from their respective details pages, allowing then the value to be found on our internal tables using cli. This commit adds the fingerprint id on the response of the statement details page. It also adds the fingerprint ID to the Statement Details page and Transaction Details page. Fixes #91763 <img width="758" alt="Screen Shot 2022-11-14 at 6 53 40 PM" src="https://user-images.githubusercontent.com/1017486/201797428-a04fcbce-e36e-426b-aeb9-bb9250adc4d6.png"> <img width="1524" alt="Screen Shot 2022-11-14 at 6 53 58 PM" src="https://user-images.githubusercontent.com/1017486/201797451-8c7035da-d2bb-4261-ad79-88618f03e7c5.png"> Release note (ui change): Add fingerprint ID in hex format to the Statement Details page and Transaction Details page. Co-authored-by: Miral Gadani <[email protected]> Co-authored-by: Andrei Matei <[email protected]> Co-authored-by: Steven Danna <[email protected]> Co-authored-by: maryliag <[email protected]>
- Loading branch information
Showing
52 changed files
with
745 additions
and
743 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
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
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
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
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.