Question about cluster node majority voting
we've been having problems db instance crashing regularly. weekend when crashed, seems have taken node on it, or separate incident...
right have 3 nodes in cluster. 2 nodes running 3 instances (2 on 1). 3rd node in state os unusable , cluster service not start.
event log:
"the failover cluster database not unloaded. if restarting cluster service not fix problem, please restart machine."
cluster log machine:
00003768.000067a0::2014/01/06-03:28:05.393 info -----------------------------+ log begin +-----------------------------
00003768.000067a0::2014/01/06-03:28:05.393 info [cs] starting clussvc service
00003768.000067a0::2014/01/06-03:28:05.394 info [cs] cluster service logging level 2
00003768.00004c30::2014/01/06-03:28:05.521 dbg [netftapi] received nsiinitialnotification
00003768.00004c30::2014/01/06-03:28:05.523 dbg [netftapi] received nsiinitialnotification
00003768.000031f4::2014/01/06-03:28:05.588 dbg [netftapi] received nsiaddinstance 169.254.3.47
00003768.00004eb4::2014/01/06-03:28:05.590 err [dm] error while restoring (refreshing) hive: status_invalid_parameter(c000000d
00003768.00004eb4::2014/01/06-03:28:05.592 err [dm] mscs::dmagent::start: status_invalid_parameter(c000000d' because of 'load(nothrow(), securityattributes, discarderror )'
00003768.00004eb4::2014/01/06-03:28:05.592 err [dm] node 3: failed unload cluster hive, error 87.
00003768.00004eb4::2014/01/06-03:28:05.592 err hive unload failed (status = 87)
00003768.00004eb4::2014/01/06-03:28:05.592 err fatalerror calling exit process.
this 3 node cluster set node majority, don't have available drive letter witness disk. since cluster service won't start, i'm not how cluster still running, thankful is.
a reboot might fix everything, i'm worried if reboot server, , cluster service still fails start... may prevent entire cluster starting , won't able run instances on other 2 nodes.
does 3rd server still act odd-number server, if cluster service won't start? if reboot , cluster service still fails start, cluster able in state , run db instances on other nodes?
i need open ms support incident on db instance crashing, i'd rather not have open 2nd 1 answer simple question.
i know if reboot server, cluster stop because there 2 nodes in majority node setup. concern if cluster service not start after reboot, cluster remain down. guessing because node voting has occurred , things running, it's staying up? i'd think cluster service being down on 1 of 3 nodes, cluster should down... it's not /phew!!
thanks in advance!
mark
node majority says nodes have votes. have 2 of 3 nodes available - hence have quorum.
"does 3rd server still act odd-number server, if cluster service won't start?" without cluster service running, node not participating in manner in cluster, not acting cluster node @ all.
you don't need drive letter witness disk. never use drive letter witness disk.
"i know if reboot server, cluster stop because there 2 nodes in majority node setup." again, if cluster service not running on third node, not providing vote. if have node majority defined quorum model, the two running nodes make quorum.
.:|:.:|:. tim
Windows Server > High Availability (Clustering)
Comments
Post a Comment