Kelly,
That is not normal. If the DB is top of the tree, and set to non
critical, it should not cause the group to offline. Even after we
introduced FaultPropagation and ManageFaults the core
Critical/Non-Critical behavior should not have changed.
Can you open a case on this?
Jim
-Original
We are testing a new SFRAC 5.0 cluster. One of the scenarios is a
"shutdown abort" to one instance. When we did this, it took the whole
group offline on that node even though the database is the top resource
in the dependency tree. Is this normal behavior? I don't remember this
every happening
