I am experiencing very slow performance on the fre...
# ask-community-for-troubleshooting
a
I am experiencing very slow performance on the freshdesk connector for airbyte while importing tickets data. Has anyone else faced the same? Is there a way to mitigate it? As an example, it took me over 5 hours to import 20000 tickets
✍️ 1
image.png
e
Hi. Based on the api docs - it`s probably an api limit. https://developers.freshdesk.com/api/#ratelimit
u
@[DEPRECATED] Marcos Marx turned this thread into Zendesk ticket 2606 to ensure timely resolution!
s
Thanks for the question @Akul Goel. I think Eli has highlighted the issue, please create an issue on Github as it shouldn’t normally be hitting the API limits. (Perhaps they modified these limits recently?)
a
That's what my initial thought was, but I have the limit set as 500, but as you can see in the above screenshot it is taking progressively longer to import the next 1000 set of batches (taking upto 40 minutes) for a batch even. This doesn't look normal to me. I'll raise an issue for it if required
i
Is there an issue in GH that I can subscribe 🔔 to?
s
@Akul Goel, did you ever raise an issue for this. If so, can you share the link here? If not, I can go ahead and create the issue if this has not been resolved yet.
i
I'm experiencing the same issue of incremental times for Airbyte 0.40.1 with latest Freshdesk connector (0.3.6).
Update: I just forked the repo and ran the connector. I'm getting a 429 with the following message:
"You have exceeded the limit of requests per hour"
. When looking at the URL I noticed that there was no
/v2/
in it. I'm guessing that's the issue but I'm still trying to catch where's happening. I just found where to fix it, will upload a PR now.
s
Thanks @Ignacio Reyna, I’ll assign someone from our maintainer program to review the PR soon.
🙌 1
a
Thanks @Ignacio Reyna for finding the issue 🙌 . @Saj Dider (Airbyte) please let me know if I should still raise an issue
r
Seems like there is an issue where the data from the source isn’t stopping for ‘tickets’ entity. The integration shows completed but the sync fails. PF the logs
@Saj Dider (Airbyte) Please do look into this issue.
m
@Rishabh D can you share the complete file log?
r
@Marcos Marx (Airbyte) Here it is.
m
From your logs:
Copy code
Caused by: io.airbyte.workers.exception.WorkerException: Source process exit with code 137. This warning is normal if the job was cancelled.
Exit code 137 means a container or pod is trying to use more memory than it’s allowed. The process gets terminated to prevent memory usage ballooning indefinitely, which could cause your host system to become unstable. You must increase the memory of the connector container/pod