https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Jonathan Druart changed:
What|Removed |Added
Blocks||35089
Referenced Bugs:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Jonathan Druart changed:
What|Removed |Added
CC||jonathan.druart+koha@gmail
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #2 from Katrin Fischer ---
I am slightly confused by this one, wasn't the idea of RabbitMQ to avoid just
this kind of thing? Having a server dealing with the jobs so nothing would be
lost and it all done in due time? It s
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
David Cook changed:
What|Removed |Added
CC||dc...@prosentient.com.au
--- C
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #4 from David Cook ---
(In reply to Nick Clemens from comment #0)
> We saw this happen several times - a library would queue up 6 batch
> modifications that would take roughly 6 minutes each.
Is that 1 job for 6 items, o
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #5 from Katrin Fischer ---
A timeout seems arbitrary when you ultimately want all jobs to be processed and
nothing be lost.
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Julian Maurice changed:
What|Removed |Added
CC||julian.maur...@biblibre.com
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #7 from Julian Maurice ---
> as soon as it receives it...
or at least as soon as it has validated that the message correspond to an
existing pending job, or something like that.
--
You are receiving this mail because:
Y
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Magnus Enger changed:
What|Removed |Added
CC||mag...@libriotech.no
--
You
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #12 from Nick Clemens ---
(In reply to David Cook from comment #4)
> (In reply to Nick Clemens from comment #0)
> > We saw this happen several times - a library would queue up 6 batch
> > modifications that would take rou
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #16 from Nick Clemens ---
(In reply to David Cook from comment #15)
> The test plan is a bit lacklustre because it's probably going to be hard for
> people to test.
>
> I suppose we can just test that it doesn't cause a
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #17 from Jonathan Druart ---
And what about the 30 minutes timeout?
--
You are receiving this mail because:
You are watching all bug changes.
___
Koha-bugs mailing list
Koha-b
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #18 from Jonathan Druart ---
I think I recreate the problem this way:
% more /etc/rabbitmq/rabbitmq.conf
consumer_timeout = 15000
Add a sleep 10 in Koha::BackgroundJob::BatchUpdateItem->process
Then enqueue several bat
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #19 from Nick Clemens ---
(In reply to Jonathan Druart from comment #18)
> I think I recreate the problem this way:
>
> % more /etc/rabbitmq/rabbitmq.conf
> consumer_timeout = 15000
>
> Add a sleep 10 in Koha::Backgroun
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Jonathan Druart changed:
What|Removed |Added
See Also||https://bugs.koha-communit
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #20 from Jonathan Druart ---
> operation basic.ack caused a channel exception precondition_failed: unknown
> delivery tag 245
I think it's the fork, I removed it and it seems to be ok now. Could someone
confirm?
> Deta
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Jonathan Druart changed:
What|Removed |Added
Severity|normal |critical
--- Comment #21
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Kyle M Hall changed:
What|Removed |Added
CC||k...@bywatersolutions.com
--
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #22 from Jonathan Druart ---
The best solution I found is the 2 patches from bug 32393.
--
You are receiving this mail because:
You are watching all bug changes.
___
Koha-bugs
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #23 from Jonathan Druart ---
(In reply to Jonathan Druart from comment #22)
> The best solution I found is the 2 patches from bug 32393.
But still not idea, I still get gaps.
--
You are receiving this mail because:
You
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #24 from Jonathan Druart ---
Created attachment 145082
-->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=145082&action=edit
Test background jobs
--
You are receiving this mail because:
You are watching a
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #25 from Jonathan Druart ---
I am giving up, need help.
I wrote this script to help adjusting the worker code and see how things went.
To test:
Edit /etc/rabbitmq/rabbitmq.conf
consumer_timeout = 1
# Delete exis
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #26 from David Cook ---
(In reply to Jonathan Druart from comment #17)
> And what about the 30 minutes timeout?
That's always a danger. If 1 message takes 30+ minutes to process, then we'll
have problems when using a "wo
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #27 from David Cook ---
(In reply to Jonathan Druart from comment #25)
> I am giving up, need help.
>
> I wrote this script to help adjusting the worker code and see how things
> went.
>
> To test:
> Edit /etc/rabbitmq/
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #28 from David Cook ---
Looks like the test plan is missing a step since without restarting the koha
background job worker you'll just get the following:
Exception 'Koha::Exception' thrown 'test is not a valid job_type'
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #29 from David Cook ---
Ok I see the timeout happening 10 seconds after it probably got the first
message on the connection/channel.
Although according to the logs it processed 51 tasks. That seems odd... I'm
going to d
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #30 from David Cook ---
I'm thinking that the prefetch config I provided isn't working with
Net::Stomp...
I enqueue 100 messages and then I look at the channel.
root@kohadevbox:kohadevbox$ rabbitmqctl list_channels
Lis
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #31 from David Cook ---
Created attachment 145134
-->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=145134&action=edit
Bug 32481: Use correct prefetch syntax for RabbitMQ
According to https://www.rabbitmq
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #32 from David Cook ---
(In reply to Jonathan Druart from comment #25)
> I am giving up, need help.
I am terribly sorry for wasting your time on this one, Jonathan.
I solved this problem on a different project using
htt
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #33 from David Cook ---
That 3rd patch "Bug 32481: Use correct prefetch syntax for RabbitMQ" uses the
correct syntax, so the worker only fetches 1 message at a time ( see
https://www.rabbitmq.com/stomp.html#pear.p )
Jona
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
David Cook changed:
What|Removed |Added
See Also||https://bugs.koha-community
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Jonathan Druart changed:
What|Removed |Added
Status|Needs Signoff |Signed Off
--
You are re
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Jonathan Druart changed:
What|Removed |Added
Attachment #144809|0 |1
is obsolete|
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Jonathan Druart changed:
What|Removed |Added
Blocks||32594
Referenced Bugs:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Nick Clemens changed:
What|Removed |Added
Status|Signed Off |Passed QA
--
You are receiv
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Nick Clemens changed:
What|Removed |Added
Attachment #145173|0 |1
is obsolete|
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Tomás Cohen Arazi changed:
What|Removed |Added
Version(s)||23.05.00
release
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #36 from Tomás Cohen Arazi ---
Pushed to master for 23.05.
Nice work everyone, thanks!
--
You are receiving this mail because:
You are watching all bug changes.
___
Koha-bugs
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Jacob O'Mara changed:
What|Removed |Added
Status|Pushed to master|Pushed to stable
Ver
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
--- Comment #37 from Jacob O'Mara ---
Nice work, thanks everyone!
Pushed to 22.11.x for the next release.
--
You are receiving this mail because:
You are watching all bug changes.
___
Ko
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Lucas Gass changed:
What|Removed |Added
Status|Pushed to stable|Pushed to oldstable
Ve
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
Arthur Suzuki changed:
What|Removed |Added
Status|Pushed to oldstable |Pushed to oldoldstable
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32481
wainuiwitikap...@catalyst.net.nz changed:
What|Removed |Added
CC||wainuiwiti
43 matches
Mail list logo