Core Server
  1. Core Server
  2. SERVER-4699

mongos can segfault after primary failover

      Details

      • Type: Bug Bug
      • Status: Closed Closed
      • Priority: Major - P3 Major - P3
      • Resolution: Fixed
      • Affects Version/s: 2.0.2
      • Fix Version/s: 2.0.3
      • Component/s: Sharding
      • Labels:
        None
      • Backport:
        Done
      • Operating System:
        ALL
      • Bug Type:
        Logical
      • # Replies:
        1
      • Last comment by Customer:
        false

        Description

        If a primary fails during a shard version reset, it's possible for the master connection to be free'd and then re-used separately.

          Issue Links

          related to

          Question - SERVER-5345 mongos crashing

          • Major - P3 - Major loss of function.
          • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

            Activity

            • Comments
            Hide
            Permalink
            Greg Studer             added a comment -

            Fix is in 2.0.3 :

            https://github.com/mongodb/mongo/commit/3eaa472e9a55c60b58446cc62c4ce3e5d420267e

            Show
            Greg Studer             added a comment - Fix is in 2.0.3 : https://github.com/mongodb/mongo/commit/3eaa472e9a55c60b58446cc62c4ce3e5d420267e

              People

              • Assignee:
                 Greg Studer
                Reporter:
                 Greg Studer
                Participants:
                Last commenter:
                Ian Whalen
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since reply:
                  2 years, 8 weeks, 1 day ago