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

Embedder too verbose #9673

Closed
rafaelromcar-parabol opened this issue Apr 26, 2024 · 0 comments · Fixed by #9718
Closed

Embedder too verbose #9673

rafaelromcar-parabol opened this issue Apr 26, 2024 · 0 comments · Fixed by #9718
Assignees
Labels

Comments

@rafaelromcar-parabol
Copy link
Contributor

Issue - Bug

  • How serious is the bug? P3
  • OS: macOS / Linux / Windows / ?
  • Browser: Chrome / Safari / Lynx / ? + version
  • Node version: node --version
  • NPM version: npm --version
  • RethinkDB version: rethinkdb --version

The Embedder logs every time a worker does not find a job on the queue with the following message

JobQueueStream: no jobs found

When using a lot of workers, the logs are very hard to follow and read.

If there are no jobs for a worker, we should not need to communicate that to the output for each worker. We already have the "jobs per second" message showing how many jobs were processed by all workers of one Embedder in the last second.

Acceptance Criteria (optional)

Embedder log show only useful information, not repeating
Triage is performed to find the root cause of the bug, timeboxed to ~1 hour.

Estimated effort: 1 hour to triage. More if root cause is already identified.

@github-project-automation github-project-automation bot moved this to To triage in Product Apr 26, 2024
@mattkrick mattkrick self-assigned this May 6, 2024
@mattkrick mattkrick moved this from To triage to In progress in Product May 6, 2024
@github-project-automation github-project-automation bot moved this from In progress to Done in Product May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants