Hi guys, i'm running a POC on my local machine try...
# replication-troubleshooting
o
Hi guys, i'm running a POC on my local machine trying to read data from ChargeBee as a source and Databricks as a destination. i ran 1 stream which work fine, then i ran the other 11 available streams from chargebee and it worked. when i ran again a SYNC it keeps failing with this error:
Copy code
2023-01-23 12:39:23 INFO i.a.w.g.DefaultReplicationWorker(getReplicationOutput):482 - failures: [ {
  "failureOrigin" : "destination",
  "internalMessage" : "io.airbyte.workers.general.DefaultReplicationWorker$DestinationException: Destination process message delivery failed",
  "externalMessage" : "Something went wrong within the destination connector",
Any idea what is this error?
n
Hi Omer, as it says in the error - something is failing in the destination. To help you debug this further I would need to see the complete logs.
o
i don't think there is much more info there
Also i noticed every time i change the number of stream it automatically restart the the job which is fine (job passes) but then immediately it starts a sync which fails as such:
@Nataly Merezhuk (Airbyte) bumping this up in case you missed 🙂
n
I'm looking into it and still don't see what might be wrong. What environment are you deploying Airbyte in? Perhaps you are running out of memory/resources?
o
i'm running it from my mac, should be enough. this is really small data. also when i run a Reset it does pass. the 'Sync now' cause this issue only
f
Hi @Omer Kolodny what is your Airbyte Version? I was testing 0.40.10 and I am facing the same issue
o
0.40.28
n
Omer, could you please open an issue for the Databricks destination connector? Please include all the logs and details there as well. Thanks
f
@Omer Kolodny are you using kubernetes?
o
No i'm using docker-compose
@Fabiano Pena are you using kubernetes?
@Nataly Merezhuk (Airbyte) i have added an issue both on github and on the discussion page
u
Thank you!
s
Hi @Omer Kolodny, did you find out what was causing this? We seem to be having a similar issue trying to pipe data from SQL Server to Databricks. Seems to happen randomly and intermittently. It can fail twice and the the third time it works without anything been changed.
o
No sorry...