Skip to content
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

fix(error): log error field in stream reader retry loop #14792

Merged
merged 2 commits into from
Jan 25, 2024

Conversation

xiangjinwu
Copy link
Contributor

@xiangjinwu xiangjinwu commented Jan 25, 2024

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

In #14755 (comment) (Unauthorized) and #14787 (unknown yet lz4 unsupported), we can only see the error message stream source reader error without knowing what the underlying error is.

On the contrary, the error message is included as a metrics label. This is an anti-pattern as error message can have high cardinality. However it is not removed in this PR to avoid breaking some people's existing workflow of checking the detailed error on grafana.

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • I have added test labels as necessary. See details.
  • I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
  • My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
  • All checks passed in ./risedev check (or alias, ./risedev c)
  • My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)
  • My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

  • My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

@github-actions github-actions bot added the type/fix Bug fix label Jan 25, 2024
"stream source reader error, actor: {:?}, source: {:?}",
self.actor_ctx.id,
core.source_id,
error = %e.as_report(),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On the sink side, an error would trigger actor exit and recovery loop, with the error Debugged with backtrace. Shall we follow the same practice here for source and switch from Display to Debug?

// Intentionally use `?` on the report to also include the backtrace.
tracing::error!(actor_id, error = ?err.as_report(), "actor exit with error");

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either LGTM

@xiangjinwu xiangjinwu requested a review from BugenZhao January 25, 2024 07:05
"stream source reader error, actor: {:?}, source: {:?}",
self.actor_ctx.id,
core.source_id,
error = %e.as_report(),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either LGTM

@xiangjinwu xiangjinwu enabled auto-merge January 25, 2024 09:14
@xiangjinwu xiangjinwu added this pull request to the merge queue Jan 25, 2024
Merged via the queue into main with commit 7cf63df Jan 25, 2024
26 of 27 checks passed
@xiangjinwu xiangjinwu deleted the fix-error-log-source-retry-loop branch January 25, 2024 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/fix Bug fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants