GetLocalSlaveOkConnection call is incorrect #12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The call to GetLocalSlaveOkConnection was adding the instance number to the mongodPort which resulted in incorrect behavior. The port number is retrieved from each local webrole instance and doesn't need to be "adjusted" since it is already correct.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The call to GetLocalSlaveOkConnection was adding the instance number to the mongodPort which resulted in incorrect behavior. The port number is retrieved from each local webrole instance and doesn't need to be "adjusted" since it is already correct.
The original code was resulting in a large number of 'Unable to connect to server localhost:27022' errors since the instance 2 (running on port 27020) was trying to test for a connection to mongod on the wrong IP address.