-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
stopper: spammy log message about throttling async task #24512
Milestone
Comments
That message isn't valuable; we should just downgrade it to log.Eventf. |
petermattis
added a commit
to petermattis/cockroach
that referenced
this issue
Apr 5, 2018
Downgrade a log message about "throttling async task" to a log event. This occurs easily for the timeseries usage of `RunLimitedAsync` task. Fixes cockroachdb#24512 Release note: None
petermattis
added a commit
to petermattis/cockroach
that referenced
this issue
Apr 5, 2018
Downgrade a log message about "throttling async task" to a log event. This occurs easily for the timeseries usage of `RunLimitedAsync` task. Fixes cockroachdb#24512 Release note: None
craig bot
added a commit
that referenced
this issue
Apr 5, 2018
24522: backport-2.0: stopper: downgrade a spammy log message to a log event r=bdarnell a=petermattis Backport 1/1 commits from #24516. /cc @cockroachdb/release --- Downgrade a log message about "throttling async task" to a log event. This occurs easily for the timeseries usage of `RunLimitedAsync` task. Fixes #24512 Release note: None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Run a local cluster and open the Admin UI and navigate to one of the dashboards. Fairly quickly you'll see a lot of log spam that looks like:
By default,
ts
uses 8 worker threads, but the admin UI graph dashboards often have many more requests.We should either remove this spammy log message or adding a flag to
RunAsyncTask
to silence it in this use case.@bdarnell, @spencerkimball Thoughts?
The text was updated successfully, but these errors were encountered: