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

process mongods are usually auto-disconnected, and sometimes we are fail to start it in hand

    XMLWordPrintable

    Details

    • Type: Question
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 2.4.4
    • Fix Version/s: None
    • Component/s: Replication
    • Environment:
      operation system:red hat linux-server-6.4-x86_64

      three Mongo config server
      three shards in every sever to back-up

      Description

      we started three mongod(correspond to three shard) in every server.afte we insert data about 1000,0000,we check the process mongods whether they are still started yet.then we find someone is stoped, the log is uploaded in the first attachement.
      another qusetion:query error,

      Mon Jul 22 10:00:30.337 [repl writer worker 1] ERROR: writer worker caught exception: BSONObj size: 1936028718 (0x2E746573) is i
      nvalid. Size must be between 0 and 16793600(16MB) First element: : ?type=116 on: { ts: Timestamp 1374316162000|168, h: -21285760
      6414574318, v: 2, op: "i", ns: "test.test", o:

      { _id: "1374316189024ec10f959daaa", C_ID: "1618", TIME: new Date(1374316189024), SE: "3", AREA: "a14", CT1: "4", CT2: "3", S_PT: 4, EN_N: "Test system", T_ID: "242", EN_T: "2", MSG: "for test35", EVENT: "test event70", S_IP: "1.2.4.138", URL: "URL257" }

      }

      how to deal with them

        Attachments

        1. 1.png
          1.png
          11 kB
        2. shard logs.txt
          6 kB

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            zhangjianchao zhangjianchao
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: