This repository has been archived by the owner. It is now read-only.
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rearrange and lengthen the watchdog delay
I did not completely comprehend that code upgrades are not atomic for all code. This watchdog ended up causing a node reboot into an unusable state because it killed couch_db_update_notifier handlers before the new code was installed for each app. This lead to mem3 quickly cycling trying to use couch_db_update_notifier which eventually took down the mem3 app which took down the node. Then the node would reboot into 1202 after databases had upgraded their headers which prevented the node from booting correctly. By extending the timeout to five minutes and placing it before the first call to terminating couch_db_update I hope to give the release enough time to complete before telling each handler to upgrade.
- Loading branch information
Showing 1 changed file with 1 addition and 1 deletion.