Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-7564

mongos crash (segfault) under load

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 2.2.0
    • Component/s: Sharding
    • Labels:
    • Environment:
      Debian 6.0 Linux vserver-dev-2 2.6.32-5-xen-amd64 #1 SMP Sun Sep 23 13:49:30 UTC 2012 x86_64 GNU/Linux, Intel E5645, HP ProLiant DL360 G7, 8GB mem. 10Krpm sata raid0

    • Linux

      The work:
      We are testing mongo for production. Right now we do only write operations, with 50 threads simultaneously. Each document is about 190bytes. We have 2 shards, and each of those two shards is a replica set with 2 members and 1 arbiter. Sharding is based on a UUID so it's pretty random. After the crash had 40280474 documents which results to about 2K inserts per second, perhaps low for this h/w.

      What happened:
      After about 5 hours of normal operation, mongos crashed with segfault. All logs are attached. (from mongos and the shards). The shards stayed operational and replica sets reported no errors when connecting to them directly after the crash. The db seems operational after mongos restart. This was our first test.

            randolph@mongodb.com Randolph Tan
            sivann Spiros Ioannou
            0 Vote for this issue
            2 Start watching this issue