Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.14.2, 1.15.1
-
None
-
None
Description
When the cluster is starting and some error occurs, the ClusterEntryPoint will shutDown the cluster asynchronous, but if it can't get a Throwable, the shutDown reason will be null, but actually if it's a user code problem and this may happen.
I think we can get the real exit reason caused by user code and pass it to the diagnostics parameter, this may help users a lot.