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

Arbiter crash with invariant failure i < _members.size()

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Incomplete
    • 3.4.6
    • None
    • Replication
    • None
    • ALL

    Description

      I just noticed this in my log files of an arbiter in a replica set with 2 other nodes.

      I'm not exactly sure which action caused this, at the time of it occuring I was doing tests that involved stopping/starting the VM that run MongoDB. The stack trace looks similar but not identical to SERVER-28079.

      The arbiter (and all other members) got restarted automatically, and seemingly the setup "recovered" without additional user interaction.

      Set up:
      This is a MongoDB 3.4.x unsharded replica set running inside kubernetes on Minikube (i.e. in a single VirtualBox VM). The MongoDB containers are managed using custom scripts.

      I'm reporting this mainly to provide a data point, given that this is a test setup it is hard to reproduce the issue in any meaningful way.

      Attachments

        Issue Links

          Activity

            People

              kelsey.schubert@mongodb.com Kelsey Schubert
              ankon Andreas Kohn
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: