xy720 opened a new pull request #4536:
URL: https://github.com/apache/incubator-doris/pull/4536


   ## Proposed changes
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. Submit a spark load job
   2. The job state is `PENDDING` at the beginning.
   3. cancel load job.
   4. Show load. And you can see the job state is `CANCELLED` with msg `user 
cancel`
   5. 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.
   
   **Expected behavior**
   The spark job should not be submmited.
   
   **The reson of this Bug**
   When a user wants to cancel a loadjob in the pending phase, it is possible 
that the `appId` in the SparkLoadJob is empty,  causing the yarn command to 
fail, so we need to get the `appId` through the handle.
   
   If the `appId` still cannot be get, the spark launcher process should be 
killed to prevent the spark mission from being submitted to yarn cluster.
   
   ## Types of changes
   
   What types of changes does your code introduce to Doris?
   _Put an `x` in the boxes that apply_
   
   - [x] Bugfix (non-breaking change which fixes an issue)
   
   ## Checklist
   
   _Put an `x` in the boxes that apply. You can also fill these out after 
creating the PR. If you're unsure about any of them, don't hesitate to ask. 
We're here to help! This is simply a reminder of what we are going to look for 
before merging your code._
   
   - [x] I have create an issue on (Fix #ISSUE), and have described the 
bug/feature there in detail
   - [x] Compiling and unit tests pass locally with my changes
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to