gtejasvi
Results
2
comments of
gtejasvi
Observed the exact same issue more than once on an instance, resolves if the read replica is restarted
seeing a similar behaviour with the history service where we are seeing that after a day of contineous usage the history service uses 100% of cpu available and comes back...