This message was deleted.

Yes, if you delete the

temporal

and

temporal_visibility

databases, Airbyte will recreate them upon restart. However, please note that this action might have some side effects. For instance, there is a chance of some running sync jobs getting stuck and they cannot be run or canceled. In such a case, you will have to reset the connector to fix it. Also, it's recommended to stop and pause all syncs before performing such maintenance tasks. Please note that this is not an official solution and it's more of a workaround that some users have found helpful. It's always recommended to backup your data before performing such operations. Sources: - [Github Issue 30691](https://github.com/airbytehq/airbyte/issues/30691) - [Github Issue 27992](https://github.com/airbytehq/airbyte/issues/27992)

> @kapa.ai Airbyte will recreate them upon restart. in the helm context, what is the restart?

In the context of Helm, a restart typically refers to stopping and then starting the services again. However, the specific process may vary depending on the configuration and setup of the services. For Airbyte, if you're running it using Docker as mentioned in one of the knowledge sources, you can restart it by first turning it off completely using the command

docker-compose down -v

and then turning it back on using

docker-compose up

[[source](https://airbyte.com/tutorials/creating-duckdb-destination-with-python)]. Please note that this process will remove the Docker volumes associated with Airbyte and you'll start from an empty database. It's important to save your configurations and data before doing this. If you're using Helm to manage your Kubernetes applications, the process might be different and you would need to refer to the specific Helm commands or Kubernetes operations for restarting services. Unfortunately, the provided knowledge sources do not contain specific instructions for restarting Airbyte using Helm. For more detailed information, you may want to refer to the official Helm documentation or the Airbyte documentation on deploying with Kubernetes.