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

TuGraph Server stopped in Docker while reporting 'UpdateDerivedVars is too Busy!' #374

Closed
jqlin2019 opened this issue Jan 12, 2024 · 3 comments

Comments

@jqlin2019
Copy link

Environment:

  • OS: Ubuntu 18.04.5 LTS
  • TuGraph-DB Version 3.5.0
  • Docker Image Version: tugraph/tugraph-runtime-centos7:3.5.0

Describe the bug

20240109080520.768: [StateMachine] bvar is busy at sampling for 2 seconds!
20240109084356.783: [StateMachine] GlobalUpdate is too busy!
20240109084453.686: [StateMachine] UpdateDerivedVars is too Busy!

I restarted the server after a few seconds.
The log was never seen before, what does that mean?
ls there too many update queries?

@lipanpan03
Copy link
Collaborator

How did you restart the server?

@lipanpan03
Copy link
Collaborator

Environment:

  • OS: Ubuntu 18.04.5 LTS
  • TuGraph-DB Version 3.5.0
  • Docker Image Version: tugraph/tugraph-runtime-centos7:3.5.0

Describe the bug

20240109080520.768: [StateMachine] bvar is busy at sampling for 2 seconds!
20240109084356.783: [StateMachine] GlobalUpdate is too busy!
20240109084453.686: [StateMachine] UpdateDerivedVars is too Busy!

I restarted the server after a few seconds. The log was never seen before, what does that mean? ls there too many update queries?

You can see the similar issue in brpc. These logs mean that the machine resources are too tight, causing the related threads of bvar::detail::SamplerCollector to be unable to obtain the cpu. So you can choose a machine with more resources.

@jqlin2019
Copy link
Author

You can see the similar apache/brpc#1239 in brpc. These logs mean that the machine resources are too tight, causing the related threads of bvar::detail::SamplerCollector to be unable to obtain the cpu. So you can choose a machine with more resources.

Thanks for your help.
I just restarted the docker containter with command docker restart containter_name.
There were some resource-intensive programs running on the machine at that time, I will pay attention to them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants