No. And, that's the unfortunate part. The o2net handshaking now includes
the timeouts so as to ensure they are the same. When we made a similar
change with config disk timeouts, we opted for the "post an error message"
in hopes users will "fix" the mismatch. Unfortunately, our experience taught
us otherwise. Now we ensure all the timeouts, net + disk, are the same for
all nodes in a cluster.
The good news is that they are very small bug fixes included in the
"potential"
1.2.5. Well, atleast till now. So there should be no reason to
immediately upgrade.
Stephan Hendl wrote:
fine, we appreciate this variable as well. Will there be a procedure for
a rolling upgrade? We are using 1.2.4 in a production environment. From
1.2.3 to 1.2.4 there whole cluster had to be offline during upgrade...
;-(
Stephan
Sunil Mushran <[EMAIL PROTECTED]> schrieb am 15.03.2007 um
20:23 in
Nachricht <[EMAIL PROTECTED]>:
Yes. 1.2.5 will have the configurable network timeout.
Randy Ramsdell wrote:
Hi,
We are planning an upgrade of an ocfs2 cluster and I wanted to
clarify
something first. Is 1.2.5 going to include a variable to set the
network
timeout? This seems to be important as we have had to move processes
off
any system running ocfs2 because the system will network timeout on
heavy load and cause the cluster to start its' kernel panic/
reboot.
Thanks,
Randy Ramsdell
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
