Uploaded image for project: 'PHP Legacy Driver'
  1. PHP Legacy Driver
  2. PHP-1536

Replica set connections randomly fail if a node is inaccessible.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: 1.6.14
    • Fix Version/s: None
    • Component/s: pecl-mongo
    • Labels:
      None
    • Environment:
      PHP 5.5.9
      Ubuntu 14.04.5
      Apache 2.4.7
      MongoDB 3.2.12
    • # Replies:
      3
    • Last comment by Customer:
      false

      Description

      We're currently running a 3-member replica set with a data-bearing secondary and an arbiter. When connecting to the replica set, web requests will randomly fail if the secondary node is either inaccessible or in an initial sync state. By "fail", I specifically mean that the web request suddenly ends without returning a response code, and no errors or exceptions are logged. Ordinary behavior during failed connect attempts to a non-replica set member results in a 500 response code and a logged exception.

      If we connect to a replica set in this state by treating the primary as a standalone (i.e. connecting directly to the primary without specifying a replica set), or if all nodes are accessible and not in an initial sync state, the connectivity problems do not appear to surface.

      Additionally, if both the primary and secondary are included in the node seed list, then the web requests fail more frequently than if only the primary is included.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            bryon.fleming Bryon Fleming
            Participants:
            Last commenter:
            Jeremy Mikola
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since reply:
              2 years, 11 weeks, 4 days ago
              Date of 1st Reply: