cancel
Showing results for 
Search instead for 
Did you mean: 

Resource created on single node

lazaur
Level 4

Hi Guys,

I configured VCS Clustered on single node and my requirement if resaouce going offline or terminated VCS should try to online it.

i set the resfault file but no luck please help. 

 
Sarfraz Qazi
Certified
1 ACCEPTED SOLUTION

Accepted Solutions

Sunil_Yadav
Level 4
Employee

Hi,

 

In case of unexpected offline/fault/termination of resource, there are 2 ways to restart.

 

                Type::RestartLimit

Type level attribute RestartLimit defines whether VCS attempts to restart a failed resource before informing of the fault. If the RestartLimit attribute is set to a non-zero value, the agent attempts to restart the resource before declaring the resource as faulted.

This is very useful if user is skeptical about particular type of resources. Set this attribute at Type level and all resources of that type will restarted. With this feature, only faulted resource is restarted. Service Group and other dependent/independent resources aren’t affected.

E.g.

type.cf snippet...
 
type Application (
.
.
        static int RestartLimit = 3
.
.
)

hatype command...

# hatype -display Application -attribute RestartLimit
#Type        Attribute              Value
Application  RestartLimit           3

In above example, all the Application resources will be retried atleast thrice in case of unexpected offline/fault/termination.

 

                Group::OnlineRetryLimit

Service Group level attribute OnlineRetryLimit allows a service group to be brought online again on the same system if a non-persistent resource in the service group faults. If, for some reason, the service group cannot be restarted, the VCS engine repeatedly tries to bring the service group online till the number of attempts that are specified by OnlineRetryLimit expires.

This is very useful if user is skeptical about particular Service Group. With this feature, entire Service Group is restarted. Thus, its useful if user wants service group to be restarted while faulted resource is restarted.

main.cf snippet...

group test_sg (
.
.
        OnlineRetryLimit = 5
.
.
        )

hagrp command...

# hagrp -modify test_sg OnlineRetryLimit 5
# hagrp -display test_sg -attribute OnlineRetryLimit
#Group       Attribute             System                 Value
test_sg      OnlineRetryLimit      localclus              5

In the above example, test_sg service group will be retried atleast 5 times if any of its resource faults.

 

Thanks & Regards,
Sunil Y

View solution in original post

5 REPLIES 5

Sunil_Yadav
Level 4
Employee

Hi,

 

In case of unexpected offline/fault/termination of resource, there are 2 ways to restart.

 

                Type::RestartLimit

Type level attribute RestartLimit defines whether VCS attempts to restart a failed resource before informing of the fault. If the RestartLimit attribute is set to a non-zero value, the agent attempts to restart the resource before declaring the resource as faulted.

This is very useful if user is skeptical about particular type of resources. Set this attribute at Type level and all resources of that type will restarted. With this feature, only faulted resource is restarted. Service Group and other dependent/independent resources aren’t affected.

E.g.

type.cf snippet...
 
type Application (
.
.
        static int RestartLimit = 3
.
.
)

hatype command...

# hatype -display Application -attribute RestartLimit
#Type        Attribute              Value
Application  RestartLimit           3

In above example, all the Application resources will be retried atleast thrice in case of unexpected offline/fault/termination.

 

                Group::OnlineRetryLimit

Service Group level attribute OnlineRetryLimit allows a service group to be brought online again on the same system if a non-persistent resource in the service group faults. If, for some reason, the service group cannot be restarted, the VCS engine repeatedly tries to bring the service group online till the number of attempts that are specified by OnlineRetryLimit expires.

This is very useful if user is skeptical about particular Service Group. With this feature, entire Service Group is restarted. Thus, its useful if user wants service group to be restarted while faulted resource is restarted.

main.cf snippet...

group test_sg (
.
.
        OnlineRetryLimit = 5
.
.
        )

hagrp command...

# hagrp -modify test_sg OnlineRetryLimit 5
# hagrp -display test_sg -attribute OnlineRetryLimit
#Group       Attribute             System                 Value
test_sg      OnlineRetryLimit      localclus              5

In the above example, test_sg service group will be retried atleast 5 times if any of its resource faults.

 

Thanks & Regards,
Sunil Y

lazaur
Level 4

Hi Sunil,
 

Thanks alots its work.

 

cheers

 
Sarfraz Qazi
Certified

mikebounds
Level 6
Partner Accredited

Please mark Sunil's post as the answer, not your own post.

Mike

Sunil_Yadav
Level 4
Employee

Thanks for pointing that out :)

Regards,
Sunil Y

Sunil_Yadav
Level 4
Employee

It’s my pleasure.

Thanks & Regards,
Sunil Y