--0__=08BBFEF7DFC601DA8f9e8a93df938690918c08BBFEF7DFC601DA
Content-type: text/plain; charset=US-ASCII
I thought it would work that way but apparently it doesn't.
I've opened a defect for the issues you noticed.
Thank you for pointing that out.
Regards,
Nilesh
informix-list-bounces@[EMAIL PROTECTED]
wrote on 06/09/2008 02:08:54 PM:
>
> ----- Original Message -----
> From: Nilesh Ozarkar
> To: Andrew Ford
> Cc: informix-list@[EMAIL PROTECTED]
; informix-list-bounces@[EMAIL PROTECTED]
> Sent: Monday, June 09, 2008 11:13 AM
> Subject: Re: Cheetah2 connection manager and failover arbitrator
>
> > I think so - depends on how you configure SLA. To avoid
> > redirection to dedicated ****t, use explicit server names in
> > SLA configuration instead of server type and avoid using the
> > dbserveralias which is configured with s=6.
>
> I tested and using explicit server names in the oncmsm.cfg file does
> not prevent a connection redirect to the other dbserver aliases
> for that engine. With my CM SLAs defined as
>
> SLA cheetah_pri=cheetah04
> SLA cheetah_sec=cheetah03
>
> I am still redirected to the cheetah04 and cheetah03 dbserver
> aliases (cheetah04_hdr and cheetah03_hdr)
>
> Even if this would work I would I would have to change the
> oncmsm.cfg file and restart CM each time a failover occurred to reflect
> the new primary and new secondary.
>
> Let me know if I misunderstood what you meant by using explicit
> server names for this config.
>
> Thanks,
>
> Andrew
>
>
> _______________________________________________
> Informix-list mailing list
> Informix-list@[EMAIL PROTECTED]
> http://www.iiug.org/mailman/listinfo/informix-list
--0__=08BBFEF7DFC601DA8f9e8a93df938690918c08BBFEF7DFC601DA
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
<html><body>
<p>I thought it would work that way but apparently it doesn't. <br>
I've opened a defect for the issues you noticed.<br>
Thank you for pointing that out.<br>
<br>
Regards,<br>
Nilesh<br>
<br>
<br>
<tt>informix-list-bounces@[EMAIL PROTECTED]
wrote on 06/09/2008 02:08:54 PM:<br>
<br>
> <br>
> ----- Original Message ----- <br>
> From: Nilesh Ozarkar<br>
> To: Andrew Ford<br>
> Cc: informix-list@[EMAIL PROTECTED]
; informix-list-bounces@[EMAIL PROTECTED]
>
> Sent: Monday, June 09, 2008 11:13 AM<br>
> Subject: Re: Cheetah2 connection manager and failover arbitrator<br>
> <br>
> > I think so - depends on how you configure SLA. To avoid<br>
> > redirection to dedicated ****t, use explicit server names in<br>
> > SLA configuration instead of server type and avoid using the<br>
> > dbserveralias which is configured with s=6.<br>
> <br>
> I tested and using explicit server names in the oncmsm.cfg file
does<br>
> not prevent a connection redirect to the other dbserver aliases <br>
> for that engine. With my CM SLAs defined as<br>
> <br>
> SLA cheetah_pri=cheetah04<br>
> SLA cheetah_sec=cheetah03<br>
> <br>
> I am still redirected to the cheetah04 and cheetah03 dbserver <br>
> aliases (cheetah04_hdr and cheetah03_hdr)<br>
> <br>
> Even if this would work I would I would have to change the <br>
> oncmsm.cfg file and restart CM each time a failover occurred to
reflect <br>
> the new primary and new secondary.<br>
> <br>
> Let me know if I misunderstood what you meant by using explicit <br>
> server names for this config.<br>
> <br>
> Thanks,<br>
> <br>
> Andrew <br>
> <br>
> <br>
> _______________________________________________<br>
> Informix-list mailing list<br>
> Informix-list@[EMAIL PROTECTED]
>
> <a
href="http://www.iiug.org/mailman/listinfo/informix-list">http://www.iiug.org/mailman/listinfo/informix-list</a><br>
</tt></body></html>
--0__=08BBFEF7DFC601DA8f9e8a93df938690918c08BBFEF7DFC601DA--
|
