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
(Note this is also about matching the redis queue names with the job class name - #2057 - assume no classes will have their names changed as a result of that ticketing, for now.)
All audit redis queue names should be prefixed with audit_
m2c should become audit_moab_to_catalog
c2m should become audit_catalog_to_moab
checksum_validation should become audit_checksum_validation
Not sure about moab_validation, as it is run by preservation_robot step and isn't really the same sort of audit -- more of a check. @justinlittman is working on understanding whether it is sometimes run as part of other three audits above - maybe ask him?
ndushay
changed the title
redis queue renames - prefix with audit or replication and match job class name
redis queue renames - prefix with audit or and match job class name
Nov 22, 2022
ndushay
changed the title
redis queue renames - prefix with audit or and match job class name
redis queue renames - prefix with audit and match job class name
Nov 22, 2022
ndushay
changed the title
redis queue renames - prefix with audit and match job class name
audit redis queue renames - prefix with audit and match job class name
Nov 22, 2022
from storytime 2022-11-21
(Note this is also about matching the redis queue names with the job class name -
#2057 - assume no classes will have their names changed as a result of that ticketing, for now.)audit_
audit_moab_to_catalog
audit_catalog_to_moab
audit_checksum_validation
Not sure about moab_validation, as it is run by preservation_robot step and isn't really the same sort of audit -- more of a check. @justinlittman is working on understanding whether it is sometimes run as part of other three audits above - maybe ask him?audit log files
Note that namespacing the audit classes for checking replication is in a separate ticket,
#2059Analogous ticket for replication queues is #2064
The text was updated successfully, but these errors were encountered: