taosdata/TDengine

WARN Acquire sch job failed, may be dropped, jobId:0x97232

Open

#31,626 opened on Jul 3, 2025

View on GitHub
 (3 comments) (0 reactions) (1 assignee)C (5,002 forks)batch import
help wantedquestion

Repository metrics

Stars
 (24,849 stars)
PR merge metrics
 (Avg merge 1d 1h) (4 merged PRs in 30d)

Description

V3.3.4.3 版本日志一直报警告： 07/03 15:44:09.313026 00000037 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x97314 07/03 15:44:09.728171 00000037 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x97315 07/03 15:44:09.728188 00000037 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x97315 07/03 15:44:12.692715 00000060 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x97316 07/03 15:44:12.692729 00000060 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x97316 07/03 15:44:15.002167 00000059 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x97317 07/03 15:44:15.002180 00000059 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x97317 07/03 15:44:15.002494 00000060 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x97318 07/03 15:44:15.002507 00000060 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x97318 07/03 15:44:15.005397 00000060 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x9731a 07/03 15:44:15.005403 00000060 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x9731a 07/03 15:44:21.829470 00000060 C QRY WARN Acquire sch job failed, may be dropped, jobId:0x9731c

Contributor guide

Research direction
Investigate the scheduler job acquisition logic in TDengine to understand why the 'Acquire sch job' fails. Look at the code paths involved in scheduling and job queues.
Tech stack
c
Domain
database
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
CDatabase internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40