TQJADE commented on code in PR #909: URL: https://github.com/apache/spark-kubernetes-operator/pull/909#discussion_r4160524172
########## docs/spark_custom_resources.md: ########## @@ -544,7 +544,12 @@ published when enabled. Since the status is not there to fall back on, it is rep minutes by default while the hold lasts, so that it outlives the event retention of the API server. An application held later, in `ScheduledToRestart`, keeps the status its previous attempt already wrote and gets the same event, since that status says that a restart is due, not that the -next attempt is withheld. +next attempt is withheld. If the driver (or master) cannot be read to check whether it was requested +already, e.g. since the API server rejects the read, the resource is neither held nor started, and +the `SuspendCheckFailed` event is published instead, until the check succeeds. A failure which may +clear on its own, such as a timeout, is retried without the event. Once the check succeeds again, +the `SuspendHeld` event may follow only with its next repeat, so a `SuspendCheckFailed` event which +is no longer refreshed no longer applies. Review Comment: updated. -- 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]
