Fractional replication is only currently allowed when the agreement destination is a read-only replica. We should allow fraction replication when the destination is a master or a hub, with the caveat that the attributes replicated for all agreements between masters are exactly the same. This change is needed to support attributes that are dynamically generated by each server instance, as is done when using the recently added memberOf plug-in.
Created attachment 296630 [details] Proposed Fix This simply removes the check to see if we're trying to use a fractional agreement with a non-read-only replica when we acquire the replica.
Your change looks good to me. It'd be nice if you could describe what happens if 2 masters have different fractional replication config from each other: "No problem" or "Error reported"?
(In reply to comment #2) > Your change looks good to me. It'd be nice if you could describe what happens > if 2 masters have different fractional replication config from each other: "No > problem" or "Error reported"? No error will be reported (at least not currently). The problems that one would encounter would be different results depending on which master you were taking to. This type of config could be done intentionally for some complex deployment, but I think it's ideal to avoid this additional complexity due to the confusion it could cause.
Created attachment 296657 [details] CVS Commit Message Checked into HEAD and Directory_Server_8_0_Branch. Thanks to Noriko for her review!
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0203.html