User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110222 Red Hat/3.1.8-4.el6_0 Lightning/1.0b2pre Thunderbird/3.1.8
On 03/09/2011 10:34 PM, Stephen Agar wrote:
In my previous reading it seemed like fractional
replication wasn't possible in a multi-master environment.
Statements like this from the administrators guide: "Fractional
replication can only be done where the consumer is a read-only
replica" are what i'm referring to. Am I misunderstanding what
fractional replication is?
It is now supported in most cases. Please direct me to statements
like the above in our docs and I will fix them.
Thanks
On Wed, Mar 9, 2011 at 11:18 AM, Rich
Megginson <rmeggins@xxxxxxxxxx>
wrote:
On 03/09/2011 10:11 AM, Stephen Agar wrote:
I've seen multiple different types
of changes in there flagged as this issue.
- Some was a custom "directory string" attribute, being
change from value notActivated to activated
I suppose this might be a problem if the schema were somehow
different between the two servers, which could happen if you
added the schema via a file and not via LDAP.
- Some password account lockout
attributes, resettime, etc.
I have a 4 server multi
master replication setup going on. We get a
lot of errors like this:
NSMMReplicationPlugin - agmt="cn="Replication
to server"" (server:636): Consumer failed to
replay change (uniqueid
2365a885-b85511df-ad54b6ca-51ecbecb, CSN
4d6ceae5000700010000): DSA is unwilling to
perform. Will retry later.
I've used cl-dump on all four nodes to dump
the logs and track these down. However, all
of the "offending" changes that say they
weren't made do indeed seem to be applied on
all 4 nodes.
What are these changes? What operations,
attributes, values, etc.
Is there a command I can use to remove
specific entries from the changelog? In the
past, i've just re-initialized nodes to get
rid of these, but that's certainly not the
preferred way to do this.