You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Version
doris-2.1.7
What's Wrong?
Around 0:00 every day, a large number of WARN logs appear in the FE (Frontend) logs, as shown below. Upon checking the related tasks in the BE (Backend), I found that the migration had already been successfully completed.
Through further investigation of the relevant code, I discovered that in the BE, a report (type=tablet) is sent to the master-FE every minute. The master then handles the task and migrates some tablets from SSD to HDD. However, during the handleMigration process, the task was not added to the AgentTaskQueue.
When the BE executes the migration task, it sends a finishTask at the end node. The master is supposed to find the task in the AgentTaskQueue based on the signature, backendId, and taskType. But since the FE did not add it to the AgentTaskQueue when submitting, this leads to the bug.
Could you please let me know if there is any reason why the task should not be added to the Queue?
Search before asking
Version
doris-2.1.7
What's Wrong?
Around 0:00 every day, a large number of WARN logs appear in the FE (Frontend) logs, as shown below. Upon checking the related tasks in the BE (Backend), I found that the migration had already been successfully completed.
Through further investigation of the relevant code, I discovered that in the BE, a report (type=tablet) is sent to the master-FE every minute. The master then handles the task and migrates some tablets from SSD to HDD. However, during the handleMigration process, the task was not added to the AgentTaskQueue.
When the BE executes the migration task, it sends a finishTask at the end node. The master is supposed to find the task in the AgentTaskQueue based on the signature, backendId, and taskType. But since the FE did not add it to the AgentTaskQueue when submitting, this leads to the bug.
Could you please let me know if there is any reason why the task should not be added to the Queue?
fe.log
be.log
fe code
be code
What You Expected?
No Warnning log in FE.
How to Reproduce?
No response
Anything Else?
Is it feasible to add the migration task to the AgentTaskQueue within the handleMigration process?
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: