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

Replication always failed

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.2.0
    • Component/s: Replication
    • Environment:
      Ubuntu 12.04 64 bits x86
    • Linux

      Hello,

      I'm facing a big issue in my production environment.
      I'v moved my standalong existing database into a replica set, and my secondary instance always failed in its initial synchronization phase.

      The failing happend on a collection named record, where indexes are defined below :
      nws_rs_1:PRIMARY> db.record.getIndexSpecs()
      [
      {
      "v" : 1,
      "key" :

      { "_id" : 1 }

      ,
      "ns" : "nadb.record",
      "name" : "id"
      },
      {
      "v" : 1,
      "key" :

      { "_id.L" : 1, "_id.K" : 1 }

      ,
      "unique" : true,
      "ns" : "nadb.record",
      "name" : "id.L_1_id.K_1",
      "dropDups" : true
      }
      ]

      nws_rs_1:PRIMARY> db.record.stats()
      {
      "ns" : "nadb.record",
      "count" : 1605239,
      "size" : 4816750020,
      "avgObjSize" : 3000.643530340342,
      "storageSize" : 8696713216,
      "numExtents" : 33,
      "nindexes" : 2,
      "lastExtentSize" : 1940869120,
      "paddingFactor" : 1.0040000005010514,
      "systemFlags" : 0,
      "userFlags" : 0,
      "totalIndexSize" : 145295696,
      "indexSizes" :

      { "_id_" : 88120928, "_id.L_1__id.K_1" : 57174768 }

      ,
      "ok" : 1
      }

      And the secondary always fails with message:
      Thu Oct 25 11:46:21 [repl writer worker 4] Fatal Assertion 15915
      (full log trace in uploaded message)

      This is a big issue since I can't set any replication mechanism !

      Thank you for you help.

      Thomas.

        1. tmp
          6 kB

            Assignee:
            kristina Kristina Chodorow (Inactive)
            Reporter:
            thomas.rosenblatt@gmail.com Thomas Rosenblatt
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: