vasu cheemakurthi
10/05/2023, 2:34 PMkapa.ai
10/05/2023, 2:34 PMairbyte-temporal. In that case, the user found that the issue was related to the configuration of their Kubernetes setup. They were able to resolve the issue by making changes to their Helm chart configuration. Specifically, they found that they needed to set resource limits for their pods. Here is the relevant extract: User: 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 User: If I look in the logs it is constantly spitting out warnings like 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``` ``` However, please note that this solution was specific to a Kubernetes deployment and may not directly apply to your situation on CentOS. If you're not using Kubernetes, the issue might be related to your network configuration or DNS settings. Unfortunately, without more specific information about your setup and the exact steps you're taking, it's difficult to provide a more precise answer. If you continue to encounter issues, I would recommend reaching out to the Airbyte community on their [Slack channel](https://airbytehq.slack.com) or [discussion forum](https://discuss.airbyte.io) for more targeted assistance.vasu cheemakurthi
10/05/2023, 2:37 PM