Uploaded image for project: 'Mongoid'
  1. Mongoid
  2. MONGOID-3891

Timeout connecting to primary node in replica set did not log an error

    • Type: Icon: Task Task
    • Resolution: Done
    • 5.0.0
    • Affects Version/s: None
    • Component/s: None
    • None

      Not sure if there is a setting that we need in our mongoid config but we recently had an issue where there was a typo setting the mongo port in our replica set. primary node had 27019 instead of 27017, the secondary had the correct port.

      We did not see any errors in our Rails log regarding the timeout to the primary. Is there a config setting that we can turn on to log this? Any insight or help will be greatly appreciated. Thanks!

            Assignee:
            Unassigned Unassigned
            Reporter:
            bitGnome bitGnome [X]
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: