dmvk commented on pull request #15501: URL: https://github.com/apache/flink/pull/15501#issuecomment-881344011
I think it should be better to use it right away as the issues this may cause would be generally hard to debug. I think to make things simpler to grasp, there could be one cached thread pool (shared between KubernetesLeaderElectionDriver and KubernetesLeaderRetrievalDriver), that we use for callbacks. Main difference between the cached pool used previously would be that submitted tasks are not long running (tied with job's execution) and threads would free up when they have nothing to do. -- 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]
