Is there some timeout on sync's? I've been running...
# replication-troubleshooting
r
Is there some timeout on sync's? I've been running a sync from stripe to snowflake, twice now on the initial sync it stops after 72 hours
Copy code
2022-10-28 14:04:21 WARN i.a.c.t.CancellationHandler$TemporalCancellationHandler(checkAndHandleCancellation):53 - Job either timed out or was cancelled.
actually not sure if this is the correct value? don't see it referenced in code other than some older tests?
Copy code
grep -inr "MAX_SYNC_TIMEOUT_DAYS" *
airbyte-tests/src/automaticMigrationAcceptanceTest/resources/env-file-migration-test-0-32-0.env:83:MAX_SYNC_TIMEOUT_DAYS=3
airbyte-tests/src/automaticMigrationAcceptanceTest/resources/docker-compose-migration-test-0-32-0-alpha.yaml:73:      - MAX_SYNC_TIMEOUT_DAYS=${MAX_SYNC_TIMEOUT_DAYS}
airbyte-tests/src/automaticMigrationAcceptanceTest/resources/docker-compose-migration-test-0-32-0-alpha.yaml:116:      - MAX_SYNC_TIMEOUT_DAYS=${MAX_SYNC_TIMEOUT_DAYS}
Copy code
SYNC_JOB_MAX_TIMEOUT_DAYS
ahh here it is
s
Was increasing the MAX_TIMEOUT_DAYS variable successful in resolving the timeout with your stripe to snowflake sync?
r
let me check, yesterday it was still running
well it got to 4+ days now.... just wish it was going faster than 1000 records a minute
Copy code
2022-11-01 16:21:41 INFO i.a.w.g.DefaultReplicationWorker(lambda$getReplicationRunnable$6):369 - Records read: 7039000 (15 GB)
2022-11-01 16:22:33 INFO i.a.w.g.DefaultReplicationWorker(lambda$getReplicationRunnable$6):369 - Records read: 7040000 (15 GB)
2022-11-01 16:23:23 INFO i.a.w.g.DefaultReplicationWorker(lambda$getReplicationRunnable$6):369 - Records read: 7041000 (15 GB)
s
Hey @Robert Put, just checking back up on this again. Did the sync finish? Not sure there’s much that can be done with the Stripe connector at the moment to make it faster. We’re aware how slow it is and there have been discussions on what to do about it.
r
Yeah after 6 days, hope I don’t need to do so in the near future haha. Thanks for responding
s
No worries, thanks for the update. Feel free to post more questions in the channel!