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

Arbiter didn't elect primary if OS is unreachable (except ping)

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.6.3
    • Component/s: Stability
    • None
    • ALL

      My VMs is hosted with ESX.

      the virtual machine that hosts my master is unreachable (ack fail)
      but the classic ping still working

      MongoDB shell version: 2.6.3
      connecting to: XXXX:27017/admin
      Socket recv() errno:104 Connection reset by peer X.X.X.X:27017

      my master from the secondary :

      	"members" : [
		{
			"_id" : 0,
			"name" : "X.X.X.X:27017",
			"health" : 1,
			"state" : 1,
			"stateStr" : "PRIMARY",
			"uptime" : 23194,
			"optime" : Timestamp(1411574324, 1),
			"optimeDate" : ISODate("2014-09-24T15:58:44Z"),
			"lastHeartbeat" : ISODate("2014-09-26T14:53:02Z"),
			"lastHeartbeatRecv" : ISODate("2014-09-26T14:53:10Z"),
			"pingMs" : 10109,
			"electionTime" : Timestamp(1411720008, 1),
			"electionDate" : ISODate("2014-09-26T08:26:48Z")
		},

      I can't even force the master ! (can't connect to ssh to modify priority)

      I'm stuck

            Assignee:
            ramon.fernandez@mongodb.com Ramon Fernandez Marina
            Reporter:
            xavier.vdb@gmail.com Xavier Vdb
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: