[Bugs] [Bug 1623749] Geo-rep: Few workers fails to start with out any failure

bugzilla at redhat.com bugzilla at redhat.com
Fri Oct 12 10:46:25 UTC 2018


--- Doc Text *updated* by Chandrakanth Pai <chpai at redhat.com> ---
Previously, workers failed during startup due to deadlock caused while waiting for the flock. When a monitor starts the workers, they update the status file by using flock to synchronize. When worker one opened the status file to update, worker two could be forked causing the file descriptor to be referenced by worker two. Since it was necessary to close the file descriptor to unlock the lock, worker one failed to unlock as the reference existed in worker two causing a deadlock for worker 2 to come up. With this fix, the flock is unlocked specifically and the status file is updated so that the reference is not leaked to any worker or agent process. As a result of this fix, all workers come up without fail.

You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=z1AqpdrO6P&a=cc_unsubscribe

More information about the Bugs mailing list