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

Secondary node failed and webservers became slow

    • Type: Icon: Task Task
    • Resolution: Done
    • 12_01_17
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      Using Mongoid version 3.1. I had a random secondary db instance failure, and noticed that my webservers became quite slow trying to connect to it but repeated failing. When I removed the dead instance from my mongoid.yml and bounced the webserver process, the issues was resolved. I wonder if there's a way to make Mongoid a bit more resilient here, such as not attempting to connect to a secondary node for a given timeout (say 30 minutes) after a series of failures?

            Assignee:
            Unassigned Unassigned
            Reporter:
            johnnyshields Johnny Shields
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: