https://linen.dev logo
Join Slack
Powered by
8 days ago we upgraded airbyte from `0.40.14` to `...
# replication-troubleshooting
r
8 days ago we upgraded airbyte from 
0.40.14
to 
0.40.22
and I see there is a specific deployment (pod in k8s) for the cron scheduler now. However, all pipelines of us which had a cron schedule configured before the upgrade are not triggered for 8 days now (we just found out) after the upgrade anymore. After re-saving the form with the cron schedule it seems to be working again, any idea what has been gone wrong here? Is this a known issue, maybe some bug in this specific version of airbyte or the related helm chart? We used helm chart version 
0.42.2
and all pods seem to be in a green state.
✅ 1
k8s state of pods:
m
@Ramon Vermeulen if you trigger manually the connections it start work again?
I didn’t see this before, not sure if an error ocurred during the upgrade process. Probably logs could help a lot
r
We put all our cron scheduled triggers on manual, and then back on cron again and it started working.
Which logs are you mainly interested in? The cron workload?
I will check if I can make an export from the whole start-up when I upgraded the helm chart
m
cron and server
r
Oh actually I think I found something interesting in the cron workload, it is green, however it has a lot of restart. What I also found is that there are no default resource limits set, I'll set some resource limits and upgrade helm chart to 
0.42.4
to see if that takes any effect
If I look in the logs it is constantly spitting out warnings like
Copy code
WARNING: [Channel<21>: (airbyte-temporal:7233)] Failed to resolve name. status=Status{code=UNAVAILABLE, description=Unable to resolve host airbyte-temporal, cause=java.lang.RuntimeException: java.net.UnknownHostException: airbyte-temporal: Name or service not known at
Basically this, and after start-up it keeps spamming the above warning
https://github.com/airbytehq/airbyte/issues/20152 this fixed it for me, but it feels like something the chart should have defaults for or at least be documented
u
There are some work in Airbyte Helm Chart but sometimes it can be unstable. Hope next quarter it become more robust. I saw you opened a PR to fix it, thanks so much!
r
No problem, I'm glad it is fixed now 🙂
Open in Slack
PreviousNext
Powered by