You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/10/08 11:07:45 UTC
[GitHub] [dolphinscheduler] HomminLee commented on issue #12196: [Question] [Worker] Start too many tasks that consume memory will cause the Worker to crash
HomminLee commented on issue #12196:
URL: https://github.com/apache/dolphinscheduler/issues/12196#issuecomment-1272294231
@SbloodyS It's nothing to do with the memory of a single task. My question is Master can't get Worker status in real time, and dispatch countless tasks to Worker.
The following picture is the master log:
<img width="1412" alt="image" src="https://user-images.githubusercontent.com/25881185/194704265-83a1dbe0-1c68-4b1c-9fde-3b14ee156e0c.png">
At time 1, worker has not enough memory, and Master failed to dispatch task to worker.
At time 2, worker finish some tasks, master know worker has enough memory by heartbeat. Then master will dispatch all tasks in queue to worker, worker will run those tasks without other check.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org