-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Source Salesforce not passing discovery phase on Kubernetes #6021
Comments
My team is experiencing this same issue with salesforce... different version info below. Airbyte version: 0.29.21-alpha It just loops back and forth between these two views. Here's the only section of logs that doesn't look like noise.
|
@marcosmarxm do we know this does work in docker? like are we sure it is a k8s problem? @sherifnada we did some saleforce stuff recently any chance it's related |
@cgardens yes, in docker took a long time because there are a lot of tables in Salesforce, but works. In Kubernetes (until I know) couldn't pass the discovery step. |
@cgardens @jrhizor based on marcos' comment above this strikes me as an issue with receiving large catalogs from the connector, rather than the connector not being able to output them at all. @mhensley-cls how many streams/tables do you have in your SF account? this would help us recreate the issue |
@sherifnada we are also observing the same error and the number of tables are 550+ |
Tweaking k8s ingress timeout fixed the issue |
Amazing, can we close this issue now @roypeter? cc: @marcosmarxm |
@misteryeo we should at least write a doc or explain here how increate the timeout in k8s for people need this. |
@cgardens agree with Marcos here. Is there someone on the platform team who could help draft these docs and tag me for review? 🙏 |
Resurfacing this @malikdiarra @andyjih can you take a look at this issue and ensure we have next steps to drive clarify for users? |
We've seen a similar issue recently as well of the discover phase failing because the catalog is too large. We can document the work around that allow people to fix that issue first. |
Cool, assignee you to take over @malikdiarra! |
@malikdiarra Please do you already have the work around documented somewhere. |
Hi @TrustOkoroego, we changed the way we store in the process the catalog during the discoverSchema phase, this should limit issues related to discovering large catalog. This was released in v0.40.12, are you using that version or a more recent one? |
I have tried to reproduce this bug by creating a Salesforce and Big Query connection, no issues were found during setup and discovery phase. Most likely it was already fixed. @YowanR can you (or somebody from TCS) please confirm if users reported such problems recently? Otherwise this issue may be closed. |
closing this issue for now, will re-open if the issue comes up again. |
Enviroment
Current Behavior
Screen.Recording.2021-09-13.at.14.02.06.mov
Expected Behavior
Tell us what should happen.
Logs
If applicable, please upload the logs from the failing operation.
For sync jobs, you can download the full logs from the UI by going to the sync attempt page and
clicking the download logs button at the top right of the logs display window.
LOG
Steps to Reproduce
Are you willing to submit a PR?
Remove this with your answer.
The text was updated successfully, but these errors were encountered: