https://linen.dev logo
Join Slack
Powered by
Hey guys. I'm having an issue with our disk gettin...
# replication-ask-ai
g
Hey guys. I'm having an issue with our disk getting full in the EKS deployment. Because of that, I'm trying to change the retention period on temporal directly but it seems another service its always changing it back to 30. Do you know what is causing it?
k
A message from kapa.ai
Yes, the retention period of the job history in Temporal is controlled by the environment variable 
TEMPORAL_HISTORY_RETENTION_IN_DAYS
. By default, it is set to 30 days. This value is also applied to the log retention when running in Docker. If you're trying to change this value directly in Temporal and it's reverting back, it's likely because Airbyte is overriding it with the value from this environment variable. To change the retention period, you should update the 
TEMPORAL_HISTORY_RETENTION_IN_DAYS
environment variable in your Airbyte configuration. For example, if you want to retain the logs for only 1 day, you can set 
TEMPORAL_HISTORY_RETENTION_IN_DAYS=1
. Please note that this change will affect both the job history in Temporal and the log retention. Make sure to consider the implications of this change on your data and operations. You can find more information about configuring Airbyte in the [official documentation](https://docs.airbyte.com/operator-guides/configuring-airbyte). Source: [Configuring Airbyte](https://docs.airbyte.com/operator-guides/configuring-airbyte)
g
I already changed the TEMPORAL_HISTORY_RETENTION_IN_DAYS and it is still set to 30, likely because this variable is ignored when deploying to Kubernetes. Do you have any idea which service could be overriding it?
p
Hi @Gabriel Martelloti, I have the same problem as you. Did you find a solution yet?
g
@Pierre CORBEL Nope. I created a github issue and I'm waiting for them to answer to it. https://github.com/airbytehq/airbyte/issues/28235
Open in Slack
PreviousNext
Powered by