tiflow engine: job xxx is not running
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 464
- Forks
- 313
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 14
Description
What did you do?
restart engine with dm job running
What did you expect to see?
job recovered
What did you see instead?
[2023/12/06 10:00:23.818 +00:00] [WARN] [job_client.go:79] ["failed to get job detail from job master"] ["response body"="{"code":"DFLOW:ErrJobNotRunning","message":"job 341412-sync is not running"}"] [url=http://dm-job-341412-tiflow-executor-0.dm-job-341412-tiflow-executor-peer.tiflow-prod-1372813089454528164-eks-ap-northeast-1-dbc303e4.svc:10241/api/v1/jobs/341412-sync/status] [status="400 Bad Request"
Versions of the cluster
Dataflow Engine version (run tiflow version):
master
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read job_client.go around line 79 and reproduce the issue by restarting the engine with a DM job running. Check the job status endpoint and compare the observed ErrJobNotRunning response with the expected recovered state; done means the job is running after restart without that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100