1) I noticed that the queue is still growing, so I added 3 more workers.
Hopefully this will be enough to catch up.
2) I don't think this is possible, the e-mail date is added by the
mailing server. Somebody correct me, if I'm wrong.
Michal
On 19. 10. 22 14:19, Vít Ondruch wrote:
First of all, thanks everybody to work on this.
However, I have two questions:
1) Will it ever catch up?
2) Could the Date of the email correspond with the event timestamp?
Vít
Dne 17. 10. 22 v 10:22 Michal Konecny napsal(a):
> Just a note, the old FMN code is living in
>
https://github.com/fedora-infra/fmn in develop branch, which is not
> default. The default one is fmn-next, which is the complete rewrite.
> So if you want to help working on current FMN, you need to start from
> develop branch.
>
> Michal
>
> On 14. 10. 22 18:32, Kevin Fenzi wrote:
>> 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
>>
>> _______________________________________________
>> infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
>> To unsubscribe send an email to
>> infrastructure-leave(a)lists.fedoraproject.org
>> 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@lists.fedora...
>> Do not reply to spam, report it:
>>
https://pagure.io/fedora-infrastructure/new_issue
> _______________________________________________
> infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-leave(a)lists.fedoraproject.org
> 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@lists.fedora...
> Do not reply to spam, report it:
>
https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org
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@lists.fedora...
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue