Hi Aurelien,
I think that the option 1 should work, the new messages in staging
should still show up in the datagrepper and I don't think anybody cares
about the messages that were already processed.
Michal
On 11. 08. 22 9:51, Aurelien Bompard wrote:
Hey folks!
There's been a report of queries long enough to cause a timeout in
datagrepper:
https://github.com/fedora-infra/datagrepper/issues/467
I don't think those queries should take so much time, and I'd like to
debug this performance issue, possibly try a couple new indexes on the
tables, etc. However, I can't reproduce the issue on staging, probably
because the datanommer database there is much smaller.
So I was wondering what is the best course of action. I see the
following options:
1. Sync the prod DB to staging. This looks like an obvious first
choice, but the messages in the staging DB actually come from the
staging environment and are used by other contributors to check that
their service is behaving properly on staging. Also, the topic prefix
of the messages is different on staging and on prod, so syncing the DB
with prod messages and then adding staging ones may cause a mess.
2. Having a second datanommer DB in prod, and syncing them. The
problem here is of course the disk space required. I don't know if
that's even possible with the hardware we have.
3. Something else?
What do you think?
Thanks!
Aurélien
_______________________________________________
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
_______________________________________________
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
