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

renameCollection within dropCollection causes signal: 11 (Segmentation fault)

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.8
    • Component/s: Storage
    • Labels:
      None
    • ALL
    • Hide

      Using mongo 4.0.8 in shard configuration: 4 replicas consisting of 3 or 2 members with arbiter. Ubuntu 16.04 in docker.

      Not quite sure how to reproduce, because on 4.0.8 version we were working for more than two weeks and all were ok until yesterday.

      Show
      Using mongo 4.0.8 in shard configuration: 4 replicas consisting of 3 or 2 members with arbiter. Ubuntu 16.04 in docker. Not quite sure how to reproduce, because on 4.0.8 version we were working for more than two weeks and all were ok until yesterday.
    • Storage NYC 2019-05-06

      Yesterday got crash of one node with error:
      2019-04-18T12:30:01.397+0300 F - [conn577437] Invalid access at address: 0
      2019-04-18T12:30:01.602+0300 F - [conn577437] Got signal: 11 (Segmentation fault).
      Replica changed primary and at night we got another crash with same error on this new primary.
      Parts of logs with crashes are included

        1. diagnostic.data.z01
          140.00 MB
          Yuriy [X]
        2. diagnostic.data.z02
          140.00 MB
          Yuriy [X]
        3. rs0-0.log
          8 kB
          Yuriy [X]
        4. rs0-2.log
          8 kB
          Yuriy [X]

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            Ubus Yuriy [X]
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: