[Date Prev][Date Next]
RE: Multiple syncrepl problems
Thanks muchly for all of this information.
We're certainly willing to put some effort into getting things work, but,
we're not very familiar with the code, so have had to rely a lot on the list
and reading the ITS for help with it.
> I note that you kept your provider 2.2.19. I'd try everything
> as 2.2.20,
> and go from there.
>From the sound of things, the main recent fixes are on the provider sides
The issue is more with having to upgrade all of our machines,
simultaneously, without breaking anything. Given that we have about a
hundred of them, you can imagine the challenge, although we are
(unfortunately, fortunately?) starting to get very good at it.
> It might also be prudent to reload your
> slave databases
> once you've got 2.2.20 squared away, just in case any of the previous
> syncRepl bugs somehow resulted in inaccurate data.
We have done this in the past, although because at the time we were
concerned with BDB corruption problems with earlier versions, and so it's
been a regular part of our upgrade procedure.
> I'm now so
> happy with 2.2.20, 2.3 will be a cautious move. I wouldn't
> have said that
> a month ago.)
Well, that's encouraging to hear. We'll keep plugging away with OpenLDAP
for a bit longer, then, before we go with an alternative. We honestly don't
want to go back to slurpd replication either, simply because we've found it
so easy for machines to get out of sync when you have so many to keep track
Thanks again for your help,
Planner, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada