-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
Description
Describe the bug
Load job's state will become incorrect after FE restart.
To Reproduce
Steps to reproduce the behavior:
Restart when the state is PENDDING
- Submit a spark load job
- The job state is
PENDDINGat the beginning. - Restart FE
- Show load. And you can see the job state is
CANCELLEDwith msgLabel [xxx] has already been used. - Open the web interface of the yarn cluster with browser, you can see that the spark job has been submitted successfully and is running well and normally.
Expected behavior
The job state should be PENDDING after FE restart.
Restart when the state is ETL
- Submit a spark load job
- Wait until the job state become
ETL - Restart FE
- Show load. And you can see the state of the job will always be stuck in ETL with progress 0%.
- Open the web interface of the yarn cluster with browser, you can see that the spark job has been submitted successfully and is running well and normally.
Expected behavior
The job state should be ETL after FE restart. And the state will not stuck in ETL.
Metadata
Metadata
Assignees
Labels
No labels