Ignore:
Timestamp:
Sep 19, 2011, 6:55:12 PM (13 years ago)
Author:
geofft
Message:
Fix notes about changelog initialization
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/server/doc/install-ldap

    r1983 r1986  
    174174       set up the servers' changelogs properly.
    175175
    176        Until this step is complete, no changes (other than the replica
    177        refresh, to initially populate the new server) should be sent, or
    178        you risk the cluster's replication agreements falling apart.
    179        Possibly disabling Pony for the duration of this setup is a good
    180        plan.
     176       If this step is not completed before any server's LDAP server
     177       shuts down, then the replication agreements will fall apart the
     178       next time a change is made. You may wish to intentionally reboot
     179       any servers that look like they want to crash _before_ beginning
     180       this process.
    181181
    182182  Here's how you do it.
    183183
    184     0. Disable Pony (we don't have a particularly good way of doing
    185        this at the moment), and tell -c scripts you're doing this and
    186        not to go off and make changes to the database until you're done.
     184    0. Tell -c scripts not to go off and reboot servers until you're
     185       done (or to get any rebooting done with first).
    187186
    188187    1. Pull open the replication part of the database. It's fairly empty
     
    317316    also good for making sure the replication agreements actually work.
    318317
    319     9. Re-enable Pony and celebrate on -c scripts.
    320 
    321318Troubleshooting
    322319===============
Note: See TracChangeset for help on using the changeset viewer.