[389-devel] revised ticket #337 - improve CLEANRUV functionality

Mark Reynolds <mareynol@xxxxxxxxxx> · Fri, 20 Apr 2012 13:05:00 -0400



    Thanks Rich and Noriko for your comments, changes applied...

    
    Thanks,

    Mark

    
    -------- Original Message --------
    
      
          Subject: 
          [389-devel] please review ticket #337 - improve CLEANRUV
            functionality
        
        
          Date: 
          Fri, 20 Apr 2012 13:05:00 -0400
        
        
          From: 
          Mark Reynolds <mareynol@xxxxxxxxxx>
        
        
          Reply-To:
          
          389 Directory server developer discussion.
            <389-devel@xxxxxxxxxxxxxxxxxxxxxxx>
        
        
          To: 
          389 Directory server developer discussion.
            <389-devel@xxxxxxxxxxxxxxxxxxxxxxx>
        
      
    https://fedorahosted.org/389/ticket/337

    
    https://fedorahosted.org/389/attachment/ticket/337/0001-Ticket-337-RFE-Improve-CLEANRUV-functionality.patch

    
     Previously the steps to remove a replica and its RUV was
      problematic. I created two new "tasks" to take care of the entire
      replication environment.

    
     [1] The new task
      "CLEANALLRUV<rid>" - run it once on any master

    
       This marks the rid as invalid. Used to reject updates to the
        changelog, and the database RUV 
       It then sends a "CLEANRUV" extended operation to each
        agreement. 
       Then it cleans its own RUV. 
    
    
       The CLEANRUV extended op then triggers that replica to send
        the same CLEANRUV extop to its replicas, then it cleans its own
        RID. Basically this operation cascades through the entire
        replication environment. 
    
     [2] The "RELEASERUV<rid>"
      task - run it once on any master

    
       Once the RUV's have been cleaned on all the replicas, you
        need to "release" the rid so that it can be reused. This
        operation also cascades through the entire replication
        environment. This also triggers changelog trimming. 
    
    For all of this to work correctly, there is a list of steps that
    needs to be followed. This procedure is attached to the ticket.

    
    https://fedorahosted.org/389/attachment/ticket/337/cleanruv-proceedure

    
    Thanks,

    Mark

    
--
389-devel mailing list
389-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-devel
--
389-devel mailing list
389-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-devel