389-devel September 2011

389-devel@lists.fedoraproject.org

3 participants
15 discussions

Please review: Bug 741744 - part2 - MOD operations with chained delete/add get back error 5, 3 on backend config
by Rich Megginson 29 Sep '11

29 Sep '11

https://bugzilla.redhat.com/show_bug.cgi?id=741744 https://bugzilla.redhat.com/attachment.cgi?id=525654&action=edit

1 0

Please review: Bug 742324 - allow nsslapd-idlistscanlimit to be set dynamically and per-user
by Rich Megginson 29 Sep '11

29 Sep '11

https://bugzilla.redhat.com/show_bug.cgi?id=742324 https://bugzilla.redhat.com/attachment.cgi?id=525606&action=edit

1 0

Please review: Bug 741744 - MOD operations with chained delete/add get back error 53 on backend config
by Rich Megginson 29 Sep '11

29 Sep '11

https://bugzilla.redhat.com/show_bug.cgi?id=741744 https://bugzilla.redhat.com/attachment.cgi?id=525605&action=edit

1 0

Please Review: (739172) Allow separate fractional attrs to be defined for incremental and total protocols
by Nathan Kinder 16 Sep '11

16 Sep '11

https://bugzilla.redhat.com/show_bug.cgi?id=739172 https://bugzilla.redhat.com/attachment.cgi?id=523589&action=edit

1 0

Please review: Make all backend operations transaction aware
by Rich Megginson 15 Sep '11

15 Sep '11

http://rmeggins.fedorapeople.org/patches/0001-Make-all-backend-operations-t…

2 1

Please review: Add support for pre/post db transaction plugins
by Rich Megginson 13 Sep '11

13 Sep '11

http://rmeggins.fedorapeople.org/patches/0001-Add-support-for-pre-post-db-t…

2 2

Please review 2: Bug 590826 - Reloading database from ldif causes changelog to emit "data no longer matches" errors
by Rich Megginson 09 Sep '11

09 Sep '11

https://bugzilla.redhat.com/show_bug.cgi?id=590826 https://bugzilla.redhat.com/attachment.cgi?id=522385&action=edit

1 0

Please review: Bug 736712 - Modifying ruv entry deadlocks server
by Rich Megginson 09 Sep '11

09 Sep '11

https://bugzilla.redhat.com/show_bug.cgi?id=736712 https://bugzilla.redhat.com/attachment.cgi?id=522382&action=edit

1 0

Please review: Bug 590826 - Reloading database from ldif causes changelog to emit "data no longer matches" errors
by Rich Megginson 09 Sep '11

09 Sep '11

https://bugzilla.redhat.com/show_bug.cgi?id=590826 https://bugzilla.redhat.com/attachment.cgi?id=522361&action=edit

1 0

about Bug 590826 - Reloading database from ldif causes changelog to emit "data no longer matches" errors
by Rich Megginson 08 Sep '11

08 Sep '11

The problem comes from the method we use to check if the changelog does not match the database in replica_check_for_data_reload(). The RUV in the database contains obsolete elements from replicas that are no longer in use. replica_check_for_data_reload() uses ruv_covers_ruv() to see if all of the max csns in the database ruv are in the changelog maxruv, and vice versa. It fails because the database ruv contains these obsolete elements not found in the changelog maxruv. My question is - why do we care? Isn't it sufficient to check that the replicageneration in the changelog is the same as the replicageneration in the database ruv? The replicageneration is supposed to be the unique identifier of the "starting point" of the replicated data. If the data is reloaded (e.g. from an ldif not created with db2ldif -r), a new replicageneration will be created, and the data will mismatch. Or, alternately, leave the check for all of the ruv elements in, but just warn if the database contains ruv elements not in the cl maxruv e.g. something like "WARNING: The database RUV contains these elements not present in the changelog max ruv: .... These elements may be obsolete, in which case you should remove them. If they are not obsolete, you should check those servers to make sure replication is occurring."

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-devel September 2011