Muralidharan

Root cause of the issue yet to be figured out.

outcome of arch call * keep existing invalid keys with punctuation etc., * delete invalid keys such as missing shared by, invalid atsign

@gkc @cconstab I parsed old prod hive storage and latest prod storage for few atsigns with my stand alone code to detect malformed keys which have to be deleted. Currently...

downgrading the severity due to other customer bugs and priorities in PR48

issue to be taken up on priority in PR51

@cconstab @cpswan Can you please grant me access to the required monitoring dashboards to help me investigate this issue

Two possible causes of CPU spike * sec check which runs every 15 mins. created inbound connection to secondary and runs scan * hive expiry check which is a scheduled...

merged PR to randomise hive expiry check https://github.com/atsign-foundation/at_server/pull/497

@cconstab @cpswan Is this issue still occurring in prod? any work to be done in the upcoming sprint related to load spikes?

> @murali-shris @cpswan should we move priority up to high for PR43 sprint planning? yes @ksanty ..we can revisit whether prod spike still exists