Failing resources doesnt cause service to fail


i have been failing resource in the msdtc cluster service, trying whole msdtc service ( shown under services , applications ) to fail per failover tab settings.

on service failover tab settings, have : 

max failures = 4

period = 6 hours.

on the resource policy tab of resource simulating failures on,  have 

period restart = 10 mins

max restarts in period = 2

if restarts fail rstart after 10 mins.

i can keep failing resource, , on 3rd within 10 mins go swap nodes expect, nevers seems lock out , go fail state after 4 attempts, expecting.

have missed or misunderstood how cluster policy should work?   understanding setting "4" max failures in specified period , after 4 simulated resource failures, whole service should fail , stay offline.

any thoughts welcome!

cheers


after fails on (on 3rd failure) come online on next node? (i expect to). once comes online, counter reset.


Windows Server  >  High Availability (Clustering)



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file