current status: We have the backend processing it's queue. The only tracebacks left are due to changes in format of fedora-messaging messages vs what it's fedmsg-meta says, which were present before on the python2 version as well. :) It's taking about 4seconds per message to find recipients, which isn't great, but hopefully will allow it to catch up. We can also look at adding some more workers (it has 6 right now). It seems to be processing/sending messages from 3 days ago right now. I think older messages are still in the queue, but got requeued at the back, so might not show up until it catches up. We still need to fix the frontend's bad redirect. Anyone who wants to help with that, help welcome. ;) I can confirm it's no longer making any fas calls at all. Hurray! So, upcoming: * Fix web redirect so people can get to the interface again. * Merge all the changes Michal and I made back to the codebase. There were a lot of changes! * There's some minor changes we could make, like replacing 'freenode' everywhere with 'librea.chat'. If anyone would like to submit PR's they would be welcome. * See if it's catching up or if we need more workers. * After f37 is out the door, I will be finally taking down fas2 and the openshift3.11 clusters. Hurray! * Eventually, the new FMN will land and replace this thing. Thanks for everyone's patience while we worked on this. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
