SQL Server Distributed Replay (Critical errors) - Active connections exceed 8192

Unanswered SQL Server Distributed Replay (Critical errors) - Active connections exceed 8192

  • 13 มิถุนายน 2555 22:34
     
     

    Hi there,I am trying replay workload from production environment using SQL Server Distributed Replay in test environment.

    My configuration is:

    • 1 Controller
    • 3 Clients
    • 1 Target SQL Server
    • synchronous mode (all other settings pretty much default)

    I have collided with the error "Active connections exceed 8192" . However, in the production environment I have not ever seen more that 1000 simultaneous connections at a time. From my perspective the error is talking about a number of all connection opened from a client during entire testing process.

    Can somebody with broad experience in this aria explain me why it is happening and what to do in order to fix it?

    There are not many documents and web-pages talking about this tool at all. Especially about errors and debugging.

    I cannot simply add 6-7 more boxes in order to exceed this limit in 8192 theoretical connection because I do not have so many connections in production and I cannot prove it to my team.

    Here is an example from Client log:

    2012-06-13 17:58:10:767 INFORMATION  [Client Replay]       All events for spid=3227 have been replayed
    2012-06-13 17:58:10:813 INFORMATION  [Client Replay]       All events for spid=3229 have been replayed
    2012-06-13 17:58:18:334 INFORMATION  [Client Replay]       All events for spid=3221 have been replayed
    2012-06-13 17:58:19:673 INFORMATION  [Client Replay]       All events for spid=3236 have been replayed
    2012-06-13 17:58:20:111 INFORMATION  [Client Replay]       All events for spid=3238 have been replayed
    2012-06-13 17:58:23:678 INFORMATION  [Client Replay]       All events for spid=3220 have been replayed
    2012-06-13 17:58:30:062 INFORMATION  [Client Replay]       Adding cursor handle mapping [180150025] -> [180150025]
    2012-06-13 17:58:30:442 INFORMATION  [Client Replay]       All events for spid=3245 have been replayed
    2012-06-13 17:58:30:513 INFORMATION  [Client Replay]       All events for spid=3248 have been replayed
    2012-06-13 17:58:30:555 INFORMATION  [Client Replay]       All events for spid=3253 have been replayed
    2012-06-13 17:58:30:597 INFORMATION  [Client Replay]       All events for spid=3250 have been replayed
    2012-06-13 18:54:00:822 CRITICAL     [Client Replay]       Active connections exceed 8192, connection 27733 is waiting.
    2012-06-13 18:58:09:997 INFORMATION  [Client Replay]       All events for spid=3222 have been replayed
    2012-06-13 18:58:09:999 CRITICAL     [Client Replay]       Active connections exceed 8192, connection 27734 is waiting.
    2012-06-13 18:58:10:018 INFORMATION  [Client Replay]       All events for spid=3234 have been replayed
    2012-06-13 18:58:10:028 CRITICAL     [Client Replay]       Active connections exceed 8192, connection 27736 is waiting.
    2012-06-13 18:58:10:672 INFORMATION  [Client Replay]       All events for spid=3257 have been replayed
    2012-06-13 18:58:10:685 CRITICAL     [Client Replay]       Active connections exceed 8192, connection 27741 is waiting.

    Controller log is clear:

    2012-06-13 10:47:38:000 OPERATIONAL  [Controller Service]  Microsoft SQL Server Distributed Replay Controller - 11.0.2100.60.
    2012-06-13 10:47:38:031 OPERATIONAL  [Controller Service]  © Microsoft Corporation.
    2012-06-13 10:47:38:047 OPERATIONAL  [Controller Service]  All rights reserved.
    2012-06-13 10:47:38:060 OPERATIONAL  [Controller Service]  Current edition is: [Enterprise Evaluation Edition].
    2012-06-13 10:47:38:061 OPERATIONAL  [Controller Service]  The number of maximum supported client is 16.
    2012-06-13 10:47:38:062 OPERATIONAL  [Controller Service]  Windows service "Microsoft SQL Server Distributed Replay Controller" has started under service account "AGILITY\alekseyf". Process ID is 2908.
    2012-06-13 10:47:38:078 OPERATIONAL  [Controller Service]  Time Zone: New Zealand Standard Time.
    2012-06-13 10:47:38:079 OPERATIONAL  [Common]              Initializing dump support.
    2012-06-13 10:47:38:080 OPERATIONAL  [Common]              Dump support is ready.
    2012-06-13 10:48:07:661 OPERATIONAL  [Controller Service]  Event replay in progress. Detailed options:
    2012-06-13 10:48:07:681 OPERATIONAL  [Controller Service]      Target DB Server: [NZ-FUSION].
    2012-06-13 10:48:07:682 OPERATIONAL  [Controller Service]      Controller Working Directory: [C:\DReplay\Trace].
    2012-06-13 10:48:07:683 OPERATIONAL  [Controller Service]      Generate Result Trace: [Yes].
    2012-06-13 10:48:07:684 OPERATIONAL  [Controller Service]      Sequencing Mode: [SYNC].
    2012-06-13 10:48:07:685 OPERATIONAL  [Controller Service]      Connect Time Scale: [100].
    2012-06-13 10:48:07:686 OPERATIONAL  [Controller Service]      Think Time Scale: [100].
    2012-06-13 10:48:07:686 OPERATIONAL  [Controller Service]      Healthmon Polling Interval: [60].
    2012-06-13 10:48:07:687 OPERATIONAL  [Controller Service]      Query Timeout: [-1].
    2012-06-13 10:48:07:688 OPERATIONAL  [Controller Service]      Data Provider Type: [ODBC].
    2012-06-13 10:48:07:689 OPERATIONAL  [Controller Service]      Threads Per Client: [512].
    2012-06-13 10:48:07:690 OPERATIONAL  [Controller Service]      Record Row Count: [Yes].
    2012-06-13 10:48:07:692 OPERATIONAL  [Controller Service]      Record Result Set: [No].
    2012-06-13 10:48:07:708 OPERATIONAL  [Controller Service]      Connection Pooling Enabled: [No].
    2012-06-13 10:48:07:723 OPERATIONAL  [Controller Service]      Stress Scale Granularity: [Connection].
    2012-06-13 10:48:07:726 OPERATIONAL  [Controller Service]      Replay Clients: [NZ-TEST03, NZ-TEST04, NZ-TEST05].
    2012-06-13 10:48:10:525 OPERATIONAL  [Controller Service]  Event dispatch in progress.
    2012-06-13 11:53:03:619 OPERATIONAL  [Controller Service]  Event dispatch completed.
    2012-06-13 11:53:03:621 OPERATIONAL  [Controller Service]  Elapsed time: 0 day(s), 1 hour(s), 4 minute(s), 55 second(s).


    • แก้ไขโดย AFomchenko 13 มิถุนายน 2555 22:36
    •  

ตอบทั้งหมด