I think there wouldn't be any problem in upgrading heartbeat. Would it
be my 2.0.8 configuration compatible?
With an unordered group, only 1 resource within the group would be
restarted?
The problem is that i need to have mounted a drbd partition before
tomcat starts. so... In some way, i need an order... but i might think
about removing this requirement provided the unordered group helps me in
my problem.
Thank you very much.
-Abraham
Dejan Muhamedagic escribió:
Hi,
On Tue, Feb 19, 2008 at 12:40:15PM +0100, Abraham Iglesias wrote:
Hi all,
I have configurede a 2 nodes v2 HA cluster with hearbeat 2.0.8. So far, I
included all resources in the same group. It is an easy way to offer
colocation and ordering features.
The problem is that I have 8 tomcat instances within the same group, so in
a loaded environment it takes 3 minutes to start all tomcat resources in
the group.
What could help is an unordered group of resources. But to do
that you'd have to upgrade, which you should do due to other
reasons as well. Can you run 2.1.3?
Thanks,
Dejan
I implemented a status function to provide every tomcat LSB script a better
way to meaure process health. Heartbeat uses this function to get the
information about resource health.
If the tomcat fails, then heartbeat restart it. That's perfect! The problem
is that in case of groups, the whole resources within a group are
restarted!!!
To improve uptime of the different services, I would like to make them
independent. I don't want "tomcat2-tomcat8" to be restarted when "tomcat1"
fails. I just want "tomcat1" to be restarted and leave all other resources
running normally in the cluster .
The problem is that all tomcats need to run in the same node. If I set
collocation constraints to INFINITY, then resources will not move to the
passive node in case of continous failure of a resource.
Anyone has some advice on how to configure colocation constraints? Or any
other solution?
Thank you very much!!
-Abraham
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
