Notices by QOTO Announcements & Polls (qoto@qoto.org)

Minor Update: So yesterday we had to tweak some resources server side, despite fixing the 503 with more resources things were still a bit sluggish. We boosted a few more resources (expanded the cluster itself) and now the system seems quite responsive as well.

Please let @freemo know if you expiernce sluggish behavior or errors.

Only thing left to fix that is broken is some UI issues with links. Some of that will actually expose features that are technically working like editing in place and translation capabilities. So as long as nothing else is broken that is more pressing we should have that fixed up in short order and then we can start working on the next version again and get out of cleanup mode.

#QOTO #Mastodon #MastoAdmin

So seems the upgrade went ok, a few small issues we should have fixed up pretty quick. Here are the broad points.

* This was our first big move over to an entirely new architecture meant for quick upgrades with no down time. Ironically this meant a 2 day down time but the advantage is future upgrades should have very minimal downtime now.

* We Did 5 upgrades in one go, lots of new features as a result, mostly all the new stuff from mastodon combined with the features QOTO already had.

* The new setup was having some 503 errors at first, and it was a out of memory issue. We have since significantly boosted our resources. The system is now much faster and responsive.

Some issues that remain, and when we will have it fixed:

* There are a few small UI issues, the link to your own profile points to the wrong link, and the "local timeline" link is missing to bring it up. We should have those back in place very shortly (probably a day or two).

* There were 503 issues periodically but it should now be fixed, please let me know if anyone sees a 503 again.

* Editing posts in place (instead of delete & edit) now works but it is missing from the menu, so we need to add that.

* Translation features should also be in place, but lacks the link.

If anyone notices any other issues message @freemo . In the meantime give us a day or two and we should have these small issues all resolved, thanks.

#QOTO #MastoAdmin #Mastodon

Just an FYI, on Thursday (2 days) we will be re-attemping our 5-in-1 update. It will be a very major update so expected as much as 3-days downtime as we are finally moving to the new architecture. We **will** be up at the other end with hopefully everything working and a few new features.

Seems our load balancer is a little under powered and its stalling momentarily from time to time. Most of you probably didnt even notice it but some of you may have.

I am going to upgrade that today to the next level. May result in up to 5 minutes down time (the new architecture will have multiple load balancers).

#QOTO

One problem fixed, another crops up...

So while that last fix did make things better, there seems to be a bit of lingering slowness for a few things, but things are mostly working.

I worked all day(and its midnight now) to bring up some very extensive monitoring tools for the team for us to help diagnose the issue.

I will work through the weekend to help improve things further, though I may need to get some sleep before I can fully resolve this. At least things are working other than a slight bit of lag. I will keep everyone on #QOTO updated.

#QOTO is back up after a short downtime. As far as I can tell the fix went smoothly. Hopefully that will address the last of the problems from migration.

In about 10 minutes #QOTO will be going down shortly in an attempt to fix a 16G table that may be at the root of one small lingering problem post migration. Luckily we have good backups and the table can always be recreated from scratch.

So should be back up shortly hopefully with the last needed fix in place and we can start the upgrades soon.

Health checks and internal networks are now in place. It went smoothly!

This should ensure that if our system crashes **for any reason** it will automatically restore itself. Should give us better uptime in the future.

#QOTO
QT: https://qoto.org/@QOTO/111988351143316298

after another short down time everything is fixed! #QOTO had to recreate an index that got lost in the migration which was slowing down the DB and everything else. No amount of resources was going to help.

But it is fixed now all ques are empty or very close to it. we will now downgrade the DB to a more sane level now that it is fixed (we upgrades shortly to maintain the system). But it will sill be a pretty hefty system for us, and we can always scale back up when needed.

TL;DR everything is wording fine now.

PS we are now going to work on a staging environment to test upgrades so we can safely start moving the main server through the upgrade cycle. stay tuned.

So we found the real problem haunting us. Turns out we didnt even need the bigger database. There was just an index that got dropped during the migration. We are working now to put it back in place. At which point things should be back up to their normal speed.

One last update before I go to bed and disapear for 12 hours.

The backlog has went from 1.2 mil at its peak earlier today to 0,4 mil now after we reconfigured things. It is steadily going down and should have everything up to working order before I get up.

One or two people were able to get images loaded after a VERY long wait. So while images still arent working it seems very likely related to the backlog. In a few hours when the backlog clears I expect image uploads should work again. If not I will check what the problem is in the morning.

Other than that most things appear to be working and everything should be functional soon.

The back log is about 2/3rds complete. This afternoon it peaked at 1.2 million and now it is ~0.4 million. I jut moved to pg_bouncer to sped that up a bit. Looks like I more than doubled the process time. Almost there.

So the Sidekiq backlog on #QOTO is still progressing. As of a few hours ago at the peak of the problem our backlog was 1.2 million jobs. As of right now its down to 0.7 million jobs. It is steadily decreasing there is just a lot to get through from the downtime. We are expecting everything to be back in working order when its done which should be around end of day. In the meantime things are still usable but you may experience very long lag on some actions.

Images still cant be uploaded, we hope this is the same problem.

As spam comes in we will block the servers on the #Fediverse. Please be patient this is happening across the whole fedi and we are working on better ways to address it.

#QOTO

#QOTO update.

So I went to bed last night and work up to find the sidekiq workers were backlogging and we have 800K backlogged jobs. It was due to a misconfiguration that I have now fixed and it appears the backlog is quickly resolving itself.

If you noticed any weirdness this should be resolved int he next few hours as the backlog clears.

#QOTO is back up.

Please keep in mind #QOTO will need quite a few hours to handle the backlog from downtime. Tomorrow we are going to split out the workers so they can begin using the scaling. So tomorrow this should be fixed. For the next 24 hours expect things to be a bit slow and uploading pictures probably wont work until we fix that.

Give it 24 hours and hopefully things will be back to normal at that time.

Please note today's server migration was moved to Friday. Expect some downtime on Friday, EST morning. We are migrating servers and begining the upgrade process for several updates we have in the pipeline. Expect brand new features in the near future.

@mapto Hi, so this is generally not a monitored account, so im sorry you didnt get a response for 5-days. I will tag the main admin and he will see this and be able to respond.

@freemo