[SPARK-36487][CORE] Modify exit executor log logic

[zwangsheng]

What changes were proposed in this pull request?

Adjust the log logic of CoarseGrainedExecutorBackend

Why are the changes needed?

When exit executor with system code 0, coarseGrainedExecutorBackend will print ERROR log.
That doesn't make sense, because it seems to me that executor's normal decommission is not caused by an exception.

Does this PR introduce any user-facing change?

no

How was this patch tested?

local

[HyukjinKwon]

can you file a JIRA please? Also it would be great to show the console output you got from the manual test.

[zwangsheng]

can you file a JIRA please? Also it would be great to show the console output you got from the manual test.

OK, i will do it later.

[zwangsheng]

Write a unit tests to reflect exitExecutor method

Using code 0 can print info log

[zwangsheng]

Please take a check, thank you. @HyukjinKwon

[yaooqinn]

ok to test

[SparkQA]

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46934/

[Ngone51]

Strictly speaking, I think this should be a user-facing change.

[Ngone51]

Sounds reasonable to me.

[SparkQA]

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46934/

[SparkQA]

Test build #142427 has finished for PR 33718 at commit 357ba65.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[AmplabJenkins]

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142427/

[yaooqinn]

LGTM

[srowen]

Merged to master