Open franTarkenton opened 1 year ago
The current process is setup to start the listener, and then it just monitors and logs the messages it receives. The process is getting rebooted every 45 minutes because it does not have a healthcheck or a liveliness probe configured. Working on adding a fastapi end point that services the health and liveliness probes. Once this is complete and implemented should get all the message events in the logs and can then start debugging why some messages don't seem to be received. ATM the message events are lost when the pod dies (every 45 minutes).
Listener now runs with a readiness and liveliness check which should eliminate the reboot of the pod every 45 minutes. Hoping that this will result in the events that we are expecting to show up in the queue to now show up. Specific events that are not included in the database are the ones for the datasets in this directory:
https://hpfx.collab.science.gc.ca/20230529/WXO-DD/model_gem_global/15km/grib2/lat_lon/00/090/
The listener has been deployed to openshift and is listening to events successfully.
downloaded the database from the server and can see the events being recorded in the db cache.
Need to figure out why subsequent events are not being triggered properly, either be a restarted process, or when all the data becomes available by the long running process.
What is happening:
What should be happening
TODO:
Def of Done: