gwcelery issueshttps://git.ligo.org/emfollow/gwcelery/-/issues2024-01-30T16:03:36Zhttps://git.ligo.org/emfollow/gwcelery/-/issues/747Make pipeline robust to external kafka broker issues2024-01-30T16:03:36ZCody MessickMake pipeline robust to external kafka broker issuesSCiMMA had issues yesterday that caused us to have redeploy everything a few times. These issues presented themselves in two ways primarily: the igwn alert topics would disappear, and the celery queue would disappear. Both of these were ...SCiMMA had issues yesterday that caused us to have redeploy everything a few times. These issues presented themselves in two ways primarily: the igwn alert topics would disappear, and the celery queue would disappear. Both of these were caught by icinga. Once these errors showed up, they wouldn't resolve themselves until the pipeline was restarted.https://git.ligo.org/emfollow/gwcelery/-/issues/737New Release Workflow Policy2024-02-22T18:35:54ZCody MessickNew Release Workflow PolicyThis is an issue to keep track of our plan to change our release workflow for O4b.
I plan to write a proposal for a new policy, which I'll add to this issue. Currently, we've discussed this on at least two calls.
The motivation to cha...This is an issue to keep track of our plan to change our release workflow for O4b.
I plan to write a proposal for a new policy, which I'll add to this issue. Currently, we've discussed this on at least two calls.
The motivation to change the release workflow is to support expedited releases that only contain emergency bug fixes (i.e. they are not just a snapshot of `main`). We had to do a release like this for v2.1.9 (#732) and it was not a smooth process, plus it introduced a release that lives on a different branch instead of on `main` like all of our previous releases.
- 23-11-21 LL technical call, Duncan shared a proposal https://git.ligo.org/emfollow/gwcelery/-/wikis/telcons/2023-11-21
- Presentation by Duncan Macleod in agenda
- There are no minutes, but just as a note: The group seemed to like Duncan's proposal in general, with the caveat that we don't change our current model of aiming to always turn `main` into a release. Duncan's proposed workflow allows for a more flexible use of main where feature development can continue on main without guarantee of going into the next release, but our project is not large enough in scope to need that functionality and we don't have enough contributors to support that workflow model anyway. We also would not change our policy of supporting only the latest release (i.e. we will not in general backport bug fixes or security patches to old releases).
- 23-11-28 LL Technical Call [agenda](https://git.ligo.org/emfollow/gwcelery/-/wikis/telcons/2023-11-28)
- Agenda contains a proposal from Roberto about implementing Duncan's suggestion.O4bCody MessickCody Messickhttps://git.ligo.org/emfollow/gwcelery/-/issues/731Follow up on broker retry deprecation warning2024-01-30T15:57:50ZCody MessickFollow up on broker retry deprecation warning```
CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine
whether broker connection retries are made during startup in Celery 6.0 and above.
If you wish to retain the existing behavior for...```
CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine
whether broker connection retries are made during startup in Celery 6.0 and above.
If you wish to retain the existing behavior for retrying connections on startup,
you should set broker_connection_retry_on_startup to True.
```https://git.ligo.org/emfollow/gwcelery/-/issues/387Move GCN notice generation from GraceDb to GWCelery2023-05-31T15:58:50ZLeo P. SingerMove GCN notice generation from GraceDb to GWCeleryMove the GCN notice generation from the GraceDb API to GWCelery to facilitate generating and sending multiple alert formats simultaneously.Move the GCN notice generation from the GraceDb API to GWCelery to facilitate generating and sending multiple alert formats simultaneously.Cody MessickCody Messick2023-05-05https://git.ligo.org/emfollow/gwcelery/-/issues/380Implement Tendis2021-10-29T14:34:08ZDeep Chatterjeedeep.chatterjee@ligo.orgImplement TendisTendis is a high-performance distributed storage system that uses Redis protocol. The claim is an application that uses Redis client should not see a difference if we swap out with Tendis. This is not urgent but might be worthwhile explo...Tendis is a high-performance distributed storage system that uses Redis protocol. The claim is an application that uses Redis client should not see a difference if we swap out with Tendis. This is not urgent but might be worthwhile exploring in the context of Redis space and memory requirements.
Suggested by Philippe Grassia: https://git.ligo.org/emfollow/gwcelery/-/issues/354#note_477536https://git.ligo.org/emfollow/gwcelery/-/issues/379Assess maxmemory-policy for redis2021-11-04T19:34:35ZGeoffrey MoAssess maxmemory-policy for redisThe current `maxmemory-policy` is set to `noeviction`. We might consider `volatile-lru` (https://redis.io/topics/lru-cache), but some digging around of the Celery source code to see what keys are given expiration times and which aren't i...The current `maxmemory-policy` is set to `noeviction`. We might consider `volatile-lru` (https://redis.io/topics/lru-cache), but some digging around of the Celery source code to see what keys are given expiration times and which aren't is required.
See https://git.ligo.org/emfollow/gwcelery/-/issues/354#note_476461