Silence exceptions when cluster is shutting down. #49
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.
I'm not sure if this is the best patch, but I did notice that close() was called elsewhere so I figured just to check for variable existence. Worst case: it showcases where the exceptions on cluster.shutdown() were coming from.
Here are the exceptions that I was getting on a normal program exit:
I realized that log was None, much like:
https://github.com/datastax/python-driver/blob/master/cassandra/cluster.py#L1526
As were _loop_lock and ConnectionShutdown.