Iterable failed after 72 hours

Connector Questions & Issues
,
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu
  • Memory / Disk: 64Gb
  • Deployment: Docker
  • Airbyte Version: 0.39.13
  • Source name/version: Iterable 0.1.15
  • Destination name/version: Snowflake (0.4.28)
  • Step: Sync
  • Description: Iterable sync pulls all non-incremental (full-refresh) streams and after 72 hours and Records read: 154512000 (71 GB), it finishes and fails.

I think looking at the logs, the sync doesn’t actually finish, it fails on the events stream. Is this an issue with iterable schema validation?

Side note, can we not have such a costly job running for 3 days and loading 70gb of data only to fail at the end?

iterable_logs.txt (63.6 KB)

2

Did you change the timeout env variable?

3

That’ll do it. Totally forgot about that. Understandable. Thanks for the reply!

4

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.