Timeout Error Fetching the Schema using AirByte Cloud and AirByte OSS

[dmcelroyfayette]

Connector Name

Netsuite

Connector Version

0.1.8

What step the error happened?

Configuring a new connector

Relevant information

The likely issue is that the source schema is too large and causing the discovery process to timeout both locally and on cloud. There was not much I could do on cloud. It would just reach the 9 minute timeout and error out. I reached out to support, but they do not support Marketplace connectors. However, they did quickly review the logs and it appeared what I was suspecting was likely the case.

When I was running AirByte OSS locally, I am using Docker Desktop and abctl. After the initial timeouts, I did some digging and made some changes to abctl.kubeconfig. I added this to the end of the file:

server:
extraEnvs:
- name: HTTP_IDLE_TIMEOUT
value: 20m
- name: READ_TIMEOUT
value: 30m

Let me know if any additional information is needed to reproduce this issue. My destination is Azure Blob Storage v0.2.4. Both the Source and Destination connection tests are still passing. Thank you for your time. Have a great day.

Relevant log output

Airbyte OSS running in Docker:  Airbyte is temporarily unavailable. Please try again. (HTTP 502)

Contribute

• Yes, I want to contribute

[natikgadzhi]

Possible. Netsuite Marketplace connector works for some cases, but not all. We have a Netsuite enterprise connector, you should talk to @matteogp about it if you need it.

[dmcelroyfayette]

Possible. NetSuite Marketplace connector works for some cases, but not all. We have a Netsuite enterprise connector, you should talk to @matteogp about it if you need it.

Thank you for mentioning that. You are correct that the other connector will work in some cases, but not ours. We would need to modify our contract to add the SuiteAnalytics Connect package to our contract which we are not interested in doing at this time. For NetSuite customers who are contracted for it, the other connector is definitely the way to go. Thank you for your response.