Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Possible fix for #1734903. #8216
Conversation
|
It is part of this. $$merge$$ |
|
Status: merge request accepted. Url: http://ci.jujucharms.com/job/github-merge-juju |
jujubot
merged commit 1a72f7b
into
juju:2.2
Dec 13, 2017
1 check passed
continuous-integration/jenkins/pr-merge
This commit looks good
Details
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
jameinel commentedDec 13, 2017
Description of change
When getting the TxnLog collection, make sure our connection is working
before we hand it back.
Without this fix, we never Refresh or Copy or Clone the underlying connection, which means if st.session ends up closed, we fail to ever work again.
QA steps
I haven't quite worked out how to test this, actually kill specific connections. Maybe there would be something with watching what Ports end up connecting to the local Mongo server, and then firewalling particular ports until you see the txn log watcher start dying indefinitely. This should allow that connection to get working again.
Documentation changes
None.
Bug reference
lp:1734903