Geo sidekiq nodes try to run jobs even thought DB is readonly
Observed in our DR/geo replica, the following jobs run and fail due to the DB being readonly:
"class":"Geo::SidekiqCronConfigWorker"
"class":"PagesDomainVerificationCronWorker"
"class":"PagesDomainVerificationWorker"
"class":"ProjectImportScheduleWorker"
"class":"UpdateAllMirrorsWorker"
mostly PagesDomainVerificationWorker and ProjectImportScheduleWorker (thousands), with the others being a fairly small number. We had to turn sidekiq off there due to the volume of logging (~700GB of elasticsearch indexes per day). Can provide more log details if it'd be helpful