-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a way to clean up old data (logs) #15567
Comments
Zendesk ticket #1884 has been linked to this issue. |
Comment made from Zendesk by Marcos Marx on 2022-08-12 at 14:04:
|
Comment made from Zendesk by Marcos Marx on 2022-08-12 at 14:17:
|
This should be addressed by #15218 |
Zendesk ticket #2096 has been linked to this issue. |
Comment made from Zendesk by Marcos Marx on 2022-08-30 at 16:23:
|
This is part of #15218 |
Comment made from Zendesk by Marcos Marx on 2022-09-01 at 17:19:
|
@marcosmarxm, #16247 re-adds a job that removes old files from the workspace. Currently, we will remove any files older than 30days by default. |
Comment made from Zendesk by Marcos Marx on 2022-09-04 at 06:07:
|
Comment made from Zendesk by Marcos Marx on 2022-09-05 at 16:47:
|
Comment made from Zendesk by Marcos Marx on 2022-09-05 at 17:41:
|
Comment made from Zendesk by Marcos Marx on 2022-09-05 at 17:42:
|
Comment made from Zendesk by Marcos Marx on 2022-09-13 at 05:22:
|
Comment made from Zendesk by Marcos Marx on 2022-09-13 at 16:16:
|
Comment made from Zendesk by Marcos Marx on 2022-09-13 at 16:17:
|
Comment made from Zendesk by Marcos Marx on 2022-09-13 at 16:22:
|
Comment made from Zendesk by Marcos Marx on 2022-09-14 at 07:20:
|
Comment made from Zendesk by Marcos Marx on 2022-09-14 at 15:05:
|
Comment made from Zendesk by Marcos Marx on 2022-09-19 at 15:38:
|
Comment made from Zendesk by Marcos Marx on 2022-09-21 at 14:05:
|
Comment made from Zendesk by Marcos Marx on 2022-11-15 at 09:19:
|
I can confirm that setting TEMPORAL_HISTORY_RETENTION_IN_DAYS does not have the expected effect. I also checked the logs and don't see any entries indicating the cleanup has started. |
@attaxia can you open a new issue to discuss the problem? Please give the complete info about your env and Airbyte platform version. |
Comment made from Zendesk by Marcos Marx on 2022-11-21 at 20:23:
|
Comment made from Zendesk by Marcos Marx on 2022-12-01 at 20:06:
|
Comment made from Zendesk by Marcos Marx on 2022-12-02 at 18:13:
|
Comment made from Zendesk by Marcos Marx on 2022-12-05 at 05:43:
|
Comment made from Zendesk by Marcos Marx on 2022-12-05 at 16:52:
|
Comment made from Zendesk by Marcos Marx on 2023-01-16 at 14:51:
|
Comment made from Zendesk by Marcos Marx on 2023-01-16 at 14:52:
|
Comment made from Zendesk by Marcos Marx on 2023-01-17 at 09:07:
|
Comment made from Zendesk by Marcos Marx on 2023-01-17 at 09:28:
|
Comment made from Zendesk by Marcos Marx on 2023-01-17 at 10:06:
|
Comment made from Zendesk by Marcos Marx on 2023-01-17 at 11:17:
|
Hey Guys, question, my EC2 instance got full due to airbyte logs. I hadn't set the TEMPORAL_HISTORY_RETENTION_IN_DAYS option. |
Tell us about the problem you're trying to solve
We no longer clean up data which can cause space issues.
It was part of the old scheduler, it has been removed temporarily and is planned to be migrated (#11869)
As a result, until that is done, we no longer offer a way to programmatically clean up space.
Describe the solution you’d like
When we deprecated the code, we kept around the former clean up code.
Could we package it as a script to manually clean up as a workaround for now?
The text was updated successfully, but these errors were encountered: