Topic
2 replies Latest Post - ‏2013-02-19T10:54:50Z by amanabe
amanabe
amanabe
59 Posts
ACCEPTED ANSWER

Pinned topic What is New TieBreaker Type "Success"

‏2013-02-14T04:48:17Z |
Hello.
My customer found TSA V3.2.2 FP3(3.2.2.3) include new TieBreaker Types.
Does someone has information about this new TieBreaker Type?

3.2.2.2
am112b:~ # lsrsrc -c IBM.TieBreaker
Resource Class Persistent Attributes for IBM.TieBreaker
resource 1:
AvailableTypes = {,,,,}

3.2.2.3
s112sa:/ # lsrsrc -c IBM.TieBreaker
Resource Class Persistent Attributes for IBM.TieBreaker
resource 1:
AvailableTypes = {,,,,,}
Thanks
Atsushi Manabe (amanabe@jp.ibm.com)
Updated on 2013-02-19T10:54:50Z at 2013-02-19T10:54:50Z by amanabe
  • Enrico_Joedecke
    Enrico_Joedecke
    109 Posts
    ACCEPTED ANSWER

    Re: What is New TieBreaker Type "Success"

    ‏2013-02-14T21:27:14Z  in response to amanabe
    Konnichiha Manabe-san,

    this new tie breaker type has been introduced by RSCT, and is described within the RSCT manuals, which are contained within the SA MP packages. Here is the excerpt:

    Success:
    A pseudo tiebreaker that is always successful in resolving a tie so that each of the subdomain has
    operational quorum. The OpQuorumState dynamic attribute of each PeerDomain resource is 0
    (HasQuorum). Therefore, if critical resources are active on a domain, they are not protected.

    So this TB type is the opposite to 'Fail', that always returns 'NoQuorum' in tie situations.
    Since SA MP is typically used for failover with critical resources, that need to be protected, I do not see an obvious use case within SA MP clusters. But in environments without critical resources (no failover, only automation) this new tb type is probably an option.

    Please let us know, if there are further questions.

    Enrico Joedecke
    • amanabe
      amanabe
      59 Posts
      ACCEPTED ANSWER

      Re: What is New TieBreaker Type "Success"

      ‏2013-02-19T10:54:50Z  in response to Enrico_Joedecke
      konnichiha Enrico-san,

      Thanks for quick answer.
      I clearly understand the new function!

      Atsushi Manabe