Hey guys! We had a cluster outage for about an hou...
# community-help
n
Hey guys! We had a cluster outage for about an hour some moments ago . Now it’s back again. But we can’t determine what happened.
apxvz0t1hbig5nuop.a1.typesense.net
. Is there a way you guys can check/pinpoint what might have caused this?
l
@Kishore Nallan can you support us here?
@Alan Martini maybe you?
πŸ‘€ 1
a
Your cluster had a crash related to JOINs. We are digging in to try to understand why this happened and if necessary, ship a fix asap
πŸ™ 3
n
Thank you for the update!
l
Hi @Alan Martini it happens again. Do you have some findings? Seams like it is a cron on our side, we will investigate it too
a
Seems like the same pattern as yesterday. Could you expand on what this cron does? (Huge importing, collections creating etc)
l
We will give you an update after our investigation. Thank you πŸ™
a
Hey Levitan, did you got any information on the investigation?
l
We revert the joins from the code, and no further investigation at the moment. The error occurred when we updated several collections via the reference field.
a
Got it. Thank you for the additional info. We actually have a know bug in a few clusters regarding this behaviour. Will update here when we have a build version with the fix.
l
Thank you for your feedback @Alan Martini
@Alan Martini do you have a timeline for the fix?
@Nurguly Ashyrov FYI
a
Hi @Levitan (Voiceops) Later this week or latest by Monday next week we should push the fix for the JOINs issue.
πŸ™Œ 1
l
Thank for that πŸ™‚
a
Hey Levitan, We've released a v31.rc1 which contains a fix for it.
πŸ™Œ 1
l
Hey Alan, thank you for your passionate support. We update this week to the latest stable version and looking forward to update to v31 as soon as it is available as stable :) great job