-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Bug] Tablet and Disk report thread not work #4597
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
[Bug] Tablet and Disk report thread not work #4597
Conversation
The tablet and disk information reporting threads need to report to the FE periodically. At the same time these two reporting threads will also be triggered by certain events. The modification in PR apache#4440 caused these two threads to be triggered only by events, and could not report regularly.
be/src/agent/task_worker_pool.cpp
Outdated
| if (status != DORIS_SUCCESS) { | ||
| DorisMetrics::instance()->report_task_requests_failed->increment(1); | ||
| LOG(WARNING) << "finish report task failed. status:" << status << ", master host:" | ||
| LOG(WARNING) << "report task failed. status:" << status << ", master host:" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| LOG(WARNING) << "report task failed. status:" << status << ", master host:" | |
| LOG(WARNING) << "report task failed. status: " << status << ", master host: " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same to other places.
be/src/olap/storage_engine.cpp
Outdated
| if (submit_task) { | ||
| TAgentTaskRequest task; | ||
| listener->submit_task(task); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems all callers pass a 'false' parameter, how about remove these code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK
|
|
||
| class TaskWorkerPool { | ||
| public: | ||
| // You need to modify the content in TYPE_STRING at the same time, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it's not easy to keep order consistency some days later, how about use a function to get name of type?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK
EmmyMiao87
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Proposed changes
The tablet and disk information reporting threads need to report to the FE periodically.
At the same time these two reporting threads will also be triggered by certain events.
The modification in PR #4440 caused these two threads to be triggered only by events,
and could not report regularly.
Types of changes