[LIVY-993][SERVER] In Livy logs, user cannot find out on whether session is deleted due to session timed out or session state retained value expired #436
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Changes done in log info so as to provide more details on the reason behind deleting the session. This will help to know the actual reason behind deleting the session
https://issues.apache.org/jira/browse/LIVY-993
How was this patch tested?
Created interactive sessions. Waited for session to be timed out. Then observed logs. In another scenario, waited for session state retained time out to expire after successfully completing the session. Then automatically session got deleted. After this, again observed logs.