Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
When we get a bad session (e.g. no registry info because AM has gone catatonic), the failure by the timeout future fails the getSession call.
The retry model in TezTask is that it would get a session (which in original model can be completely unusable, but we still get the object), and then retry (reopen) if it's a lemon. If the reopen fails, we fail.
getSession is not covered by this retry scheme, and should thus do its own retries (or the retry logic needs to be changed)
Attachments
Attachments
Issue Links
- links to