Error: Operator called default onErrorDropped when HealthMonitorTask.monitor job can't be started due to termination of a pod

[iNviNho]

Expected Behavior

Hi,

We see an error log that HealthMonitorTask.monitor can't be scheduled. Based on the exception stack trace and further investigation, it happens rarely and only when k8s pod is terminated.

I would expect that there is no error log as the pod is terminating and it is obvious that scheduler can't be run as threadpools are getting closed.

Actual Behaviour

The stack trace looks like this

eactor.core.Exceptions$ErrorCallbackNotImplemented: reactor.core.Exceptions$ReactorRejectedExecutionException: Scheduler unavailable
Caused by: reactor.core.Exceptions$ReactorRejectedExecutionException: Scheduler unavailable
....
io.micronaut.management.health.monitor.HealthMonitorTask.monitor(HealthMonitorTask.java:97)
	at io.micronaut.management.health.monitor.$HealthMonitorTask$Definition$Exec.dispatch(Unknown Source)
...
Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@47388a61[Not completed, task = io.micrometer.core.instrument.Timer$$Lambda/0x00007f3e3d2afb20@430706d9] rejected from java.util.concurrent.ThreadPoolExecutor@64cc5f34[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 870]
```stack trace

### Steps To Reproduce

_No response_

### Environment Information

java:21

### Example Application

_No response_

### Version

4.3.8