my patch idea has been working for me. when an sql timeout occurs on the 1st dbsource it will skip to the 2nd dbsource. But, if the sql timeout occurs on the 2nd source, rather than try the 3rd source, it starts again with the 1st. So, a reoccurring timeout issue will bounce between the 1st source and 2nd sources only.
This is good enough for me, but there's probably a better way. Maybe rotate the dbsources instead of trying starting from the 1st source. But, on the other hand, it's also nice to have radiator prefer the 1st db source instead of rotating. I'd rather have radiator prefer the 1st source as I have it configured always as 'localhost'. On 11-08-19 03:46 AM, Heikki Vatiainen wrote: > On 08/18/2011 03:50 AM, Michael wrote: > >> > I'm still testing/monitoring it to. So far, it will just alternate >> > between the first 2 sql sources. I have 4. I wanted to keep the 1st sql >> > source preferred. My patch may not be a desired solution, but here it is: > Thanks for the patch. If you need to change something or notice > something that might be of interest, please let us know. We are > interested to hear how your approach works. > > We are considering changes to the error behaviour and as I wrote, also > thinking about how to do it so that the changes will not negatively > change existing configurations. > _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
