This message was deleted.
# community-help
s
This message was deleted.
j
Looking now
k
Thanks!
j
Looks like you’re on an early build that had a couple of validation issues that stalled the write queue we’ve fixed since in recent RC builds…
k
Can we do an in-place upgrade?
j
Yup, I can queue that up for you, once we stabilize this node with the stalled write queue
Working on it
k
You’re the best
😄 1
j
@Keith Petrillo You’re all set. Your cluster is now running 0.24.1 and that version doesn’t have this particular issue
k
Awesome! Thank you so much 🙏
j
Happy to help!
k
Do you know if any way we could put alerts around those stats?
It went a week without us noticing to be honest
j
For this particular case where writes were stalled, but searches were working fine, I would recommend monitoring the HTTP response codes from Typesense and monitoring for any anomalies there…
If both reads and writes were stalled, then our monitoring would have flagged this…
k
Do we get notifications on those?
Rather, are we suppose to?
j
No, we receive pages on our side for anything that affects both reads and writes, and in most cases we’re able to resolve them by upgrading capacity for eg (when auto capacity scaling is enabled).
In other cases, if we need additional info to stabilize the cluster, we then email customers
k
AH gotcha, no problem, I’m sure I could whip up a monitoring tool