Skip to get the batch application status when creating batch#4680
Skip to get the batch application status when creating batch#4680turboFei wants to merge 1 commit intoapache:masterfrom
Conversation
turboFei
changed the title
|
How can we return app id if we do not get application status when creating batch ? Do you mean we do not need to return app related info when creating batch ? |
Yes, the key information is batchId. |
|
cc @pan3793 not sure if it breaks your customer .. |
|
I think that usually the response for create batch request should be returned in milliseconds. So, it is impossible to get the application status in most cases. |
What's the current result in your production case? NOT_FOUND or UNKNOWN? |
|
It is none, I think. |
|
We have UNKNOWN state, why should return null/None instead? |
|
cc @zwangsheng as well |
|
I'm + 1 for get And using timeout to check whether submit success or not. Unknown sounds more reasonable, when we submit but can fount app. |
4 participants
Why are the changes needed?
To prevent the
POST /batchesoperation stuck when getting batch application status.For example: the yarn client always failover because of resource manager issue.
And it is also not needed that get the batch app status info when creating batch.
How was this patch tested?
Add some test cases that check the changes thoroughly including negative and positive cases if possible
Add screenshots for manual tests if appropriate
Run test locally before make a pull request