Open joshua-pgatour opened 6 months ago
@joshua-pgatour what CLI version is this with?
I merged a fix related to this in https://github.com/datahub-project/datahub/pull/9967
Thank you for the reply. I have tried going back one version at a time on datahub-actions dockerhub releases and the KeyError seems to stop happening around v10. However, I still have a memory issue. I have pretty much maxed out the size my pod can be and it still fails with memory SIGKILL. Any suggestions on getting around this? Here is my current recipe:
`source:
type: redshift
config:
host_port: '
`
So I figured out how to change the CLI version in the ingest recipe. I'm sorry I thought it was controlled by the datahub-actions container version. (Didn't know it was controlled in the recipe). 0.10.5.1 CLI works fine on 16gb memory and there is no KeyError. I will experiment at what point this breaks. But I gotta believe there's a memory leak in newer versions.
I can confirm that v0.13.2 has the memory problem. v0.13.1 works, but in my testing the ingest process has slowed significantly since 0.12
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
@joshua-pgatour regarding memory utilization - this should help https://github.com/datahub-project/datahub/pull/10691
If the issue persists, it'd be helpful to have a memory profile generated as per https://datahubproject.io/docs/metadata-ingestion/docs/dev_guides/profiling_ingestions/
Describe the bug