Uploaded image for project: 'C# Driver'
  1. C# Driver
  2. CSHARP-1435

System.TimeoutException: A timeout occured after 30000ms selecting a server using CompositeServerSelector{

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Blocker - P1 Blocker - P1
    • None
    • Affects Version/s: 2.0.1
    • Component/s: API
    • None
    • Environment:
      Mongodb 2.6.11 - Cluster with one replicaset - Connection to shared routers

      In heavy CPU loading condition our Web Application Get Stucked.

      All threads are blocked and after 30 second in the log are added those errors:

      [ERROR] - 20151005 13:15:02:97615 - RequestId=1a863907-853e-41f7-8ea7-7d84ee81db83|RequestId=1a863907-853e-41f7-8ea7-7d84ee81db83|Error on EntityController.OnException
      System.TimeoutException: A timeout occured after 30000ms selecting a server using CompositeServerSelector{ Selectors = WritableServerSelector, LatencyLimitingServerSelector

      { AllowedLatencyRange = 00:00:00.0150000 }

      }. Client view of cluster state is { ClusterId : "1", Type : "Sharded", State : "Disconnected", Servers : [{ ServerId: "

      { ClusterId : 1, EndPoint : "Unspecified/mywapp1:27017" }

      ", EndPoint: "Unspecified/mywapp1:27017", State: "Disconnected", Type: "Unknown" }, { ServerId: "

      { ClusterId : 1, EndPoint : "Unspecified/mywapp2:27017" }

      ", EndPoint: "Unspecified/mywapp2:27017", State: "Disconnected", Type: "Unknown" }] }.

      As you can see all nodes are disconnected.

      This is our connection string:

      mongodb://dbuser:XXXXXXXXX@mywapp1,mywapp2/?connect=ShardRouter&maxPoolSize=500&minPoolSize=50

        1. Issue 2015-10-05.zip
          362 kB
        2. mongos_mywapp1.log
          9.70 MB
        3. mongos_mywapp2.log
          9.90 MB

            Assignee:
            craig.wilson@mongodb.com Craig Wilson
            Reporter:
            lucacasali Luca casali
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: