Page History

...

• Run the usage server in a multi-threaded mode (usage server is taking a lot of time, seems like single-threaded). Explore/PoC if multiple nodes can be active at the same time.
• Usage server related APIs to work with specified domainid/accountid and specific usage types (example: regenerating data for a certain usage type on a time interval).
• In case of duplicates where healing is possible, the usage job must continue running and fix the issue. In other case, an email or alert must be sent to the administrator for repairing.
• Create an API to re-generate records between a start and end date (delete records for a slice of time/dates and insert new regenerated usage data records). Assumption: having accounts, events, and helper tables to regenerate usage data.
• Add a global setting to set the number of years (minimum 1 year as default for fresh installations, and default value = 0 upon upgrade for backward compatibility) to keep the usage data and remove the older usage data.
• Refactor and extend the sanity check task to ensure the usage types are covered, report any errors in a separate sanity check logs and send an email to the administrator.

...