-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Queued Export Failing Silently communication link failure #44
Comments
Which queue driver are you using? |
We tested with redis and database. The issue happens on both drivers database and redis i was able to understand the error while using the database driver |
Do you have a stack trace for the exception that happens when using redis perhaps? |
Not really the queue is failing silently when we run the queue workers as daemon. So we suspect a memory leak issue. |
Can you check the redis log ( |
Yes for sure basically the only thing i see is the following: |
Sounds indeed like to big of a job to save. Could you perhaps share a bit more of your code? Seems like something on your nova resources is a lot bigger than it is for us. Perhaps something we don't even need to serialize. |
Sorry for the late reply.. Yes for sure this is the user resource:
}` It's a huge resource but as you can see we only try to export just a few fields |
Can you try commenting out all the stuff that is not used in the export and see how much better that performs? Using ->only() doesn't remove stuff from the resource, only doesn't add it to the export. |
Ok i reduced the fields that i are used for the export and removed all the other. Still didn't manage to do a successful export they processing slows down after a few AppendQueryToSheet and then stops without an error... `art queue:work sudo tail /var/log/redis/redis-server.log |
Can you try to increase the chunk size? |
Yes I already did with no luck Just to clarify i am testing the exports for 256k database records |
I'll see if I can reproduce it soon. |
Ok thanks i'll give it a go |
|
Perhaps a bit smaller than 20 000 then 🤣 |
Don't know if it helps but i was able to make it work with chunk count 15 000 and instead of using the |
With listen it spans up a new instance of Laravel on each job, it might have positive influence on this. I'll see if we can improve the serialization part. |
Hey @gpanos I've perhaps found a workaround. Can you test it on the 1.1 branch perhaps? |
@patrickbrouwers for sure i'll give it a go asap thanks!! FYI we went for our own implementation since we were in a hurry to deliver using league-csv behind the scenes heavily influenced from your implementation. I let you know as soon as i test thanks again for the great work! |
Prerequisites
Versions
Description
When trying to do a queued export (tried with both database and redis) it fails silently without throwing any error or having any failed jobs. After investigating further the queue processing stops at
Processing: Maatwebsite\Excel\Jobs\AppendQueryToSheet i opened the logs (when using the database driver) and i saw the error communication link failure: 1153 Got a packet bigger than max_allowed_packet bytes. From what i understand it tries to serialize a huge request object and fails.
Steps to Reproduce
Expected behavior:
Queue excel exports
Actual behavior:
Excel export queuing fails everytime no matter how large the selected dataset is.
Any help will be greatly appreciated thanks in advance!
The text was updated successfully, but these errors were encountered: