Changes between Initial Version and Version 1 of Ticket #174


Ignore:
Timestamp:
Sep 27, 2010, 4:18:06 PM (14 years ago)
Author:
ezyang
Comment:

Rewrote proposal based on conversation with Mitch.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #174

    • Property Summary changed from Nagios plugin to ensure replication generations are correct to Nagios plugin to check for different generation ID error message

  • Ticket #174 – Description

    initial v1  
    1 In the nsds50ruv attribute, replication agreements record a "generation ID" which prevents two masters initialized from different sources from attempting to overwrite each other and cause a mess. Unfortunately, this safety mechanism also means that replication doesn't work, and furthermore, while this will result in a lot of spew to the LDAP error log, this won't show up in the usual status field.  We should check that all of the replication generations on our servers are consistent.
     1Check for the error message:
     2
     3{{{
     4[23/Sep/2010:15:18:56 -0400] NSMMReplicationPlugin - agmt="cn="GSSAPI
     5Replication to whole-enchilada.mit.edu"" (whole-enchilada:389): Replica has a
     6different generation ID than the local data.
     7}}}
     8
     9which indicates something has gone wrong with replication. This message does not appear to be picked up by our existing MMR checks.
     10
     11Old text: ''In the nsds50ruv attribute, replication agreements record a "generation ID" which prevents two masters initialized from different sources from attempting to overwrite each other and cause a mess. Unfortunately, this safety mechanism also means that replication doesn't work, and furthermore, while this will result in a lot of spew to the LDAP error log, this won't show up in the usual status field.  We should check that all of the replication generations on our servers are consistent.''