dongjoon-hyun opened a new pull request, #36707:
URL: https://github.com/apache/spark/pull/36707

   ### What changes were proposed in this pull request?
   
   This PR aims to log `ExecutorDecommission` as INFO level in 
`TaskSchedulerImpl`.
   
   ### Why are the changes needed?
   
   Like the other modules, `TaskSchedulerImpl` had better log the decommission 
as `INFO` level instead of `ERROR`.
   ```
   22/05/28 01:25:28 INFO KubernetesClusterSchedulerBackend: Decommission 
executors: 8
   22/05/28 01:25:28 INFO KubernetesClusterSchedulerBackend: Notify executor 8 
to decommissioning.
   22/05/28 01:25:28 INFO BlockManagerMasterEndpoint: Mark BlockManagers 
(BlockManagerId(8, 100.103.40.13, 43353, None)) as being decommissioning.
   22/05/28 01:25:29 ERROR TaskSchedulerImpl: Lost executor 8 on 100.103.40.13: 
Executor decommission.
   22/05/28 01:25:29 INFO ExecutorMonitor: Executor 8 is removed. Remove reason 
statistics: ...
   22/05/28 01:25:29 INFO DAGScheduler: Executor lost: 8 (epoch 7)
   22/05/28 01:25:29 INFO BlockManagerMasterEndpoint: Trying to remove executor 
8 from BlockManagerMaster.
   22/05/28 01:25:29 INFO BlockManagerMasterEndpoint: Removing block manager 
BlockManagerId(8, 100.103.40.13, 43353, None)
   22/05/28 01:25:29 INFO BlockManagerMaster: Removed 8 successfully in 
removeExecutor
   22/05/28 01:25:29 INFO DAGScheduler: Shuffle files lost for executor: 8 
(epoch 7)
   22/05/28 01:25:34 INFO BlockManagerMaster: Removal of executor 8 requested
   22/05/28 01:25:34 INFO BlockManagerMasterEndpoint: Trying to remove executor 
8 from BlockManagerMaster.
   22/05/28 01:25:34 INFO 
KubernetesClusterSchedulerBackend$KubernetesDriverEndpoint: Asked to remove 
non-existent executor 8
   ```
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. This is a change on log level.
   
   ### How was this patch tested?
   
   Pass the CIs.


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

To unsubscribe, e-mail: [email protected]

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