You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other alternatives are a) store a flag in the database b) A lock on the shared file (if read-only file system this will not work)
API need to be exposed to a) write the flag to database. b) remove the flag.
Bynar needs to re-evaluate if flag set is for too long.
In protobuf, add two messages: one for putting a Bynar daemon into "maintenance mode"; another for getting it out of maintenance mode.
If we go with the DB-centric way:
Use Case: Set to Maintenance
Upon receiving a setMaintenance message, the daemon will call the SQL DB to set the 'status' column to "maintenance" or some string.
Whenever the daemon accepts a request, it will then check the SQL db to see if itself is in maintenance mode, if so, log it and get out without doing anything (ignore all request).
Use Case: Unset Maintenance
Upon receiving a unsetMaintenance message, the daemon will call the SQL DB to set the status back to "running"(?)
From then on, the daemon will perform usual duties to check disks/etc as usual.
Anything better we can come up with besides just disabling the cron job while maintenance is being performed on a server?
The text was updated successfully, but these errors were encountered: