[389-devel] Please review: [389 Project] #335: transaction retries need to be cache aware

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fix description:
 When libdb returns DEADLOCK and backend update function retries
 the operation, the target entry is reset to the original shape.
 The target entry could be or could not be in the entry cache.
 Regardless of the status, the original code just released the
 entry with backentry_free before going into the next loop, which
 causes the cache error.

 This patch checks the status of the entry.  If it is in the entry
 cache, remove it from the entry cache and add a new entry back to
 the cache if necessary.  To get the accurate cache status of each
 entry, the output argument cache_res to id2entry_add_ext is added.

 Additinally, error checking for the conflict value in index_add_mods
 was week (curr_attr).  This patch is adding the check.

389-devel mailing list

[Fedora Directory Announce]     [Older Fedora Users Mail]     [Home]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [iPod Nano]     [ATA RAID]     [Fedora Bible]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Review]     [Fedora Art]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Tux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]

Powered by Linux