juju shouldn't let txn-queues grow out of control
Bug #1778907 reported by
Junien F
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
2.3 |
Fix Released
|
High
|
John A Meinel |
Bug Description
Hi,
We got it by a bug today where the txn-resumer was unable to resume a transaction (because of a bug in the code).
In less than 2 days, the txn-queue for a few documents grew to over 25k. We thankfully caught the problem relatively fast and were able to deal with it, but agents now need to process these 25k txns.
If an operation fails, juju shouldn't let txn-queues grow out of control because of constant retries.
Thanks
summary: |
- juju shouldn't let txn-queues growing out of control + juju shouldn't let txn-queues grow out of control |
To post a comment you must log in.
What version of Juju was running? We have put some changes in place to
avoid letting the Queue grow too large. I believe we had a release bug
where early 2.3 releases weren't getting all of the patches for our
dependencies.
John
=:->
On Wed, Jun 27, 2018, 16:30 Junien Fridrick <email address hidden>
wrote:
> Public bug reported: /bugs.launchpad .net/bugs/ 1778907 /bugs.launchpad .net/juju/ +bug/1778907/ +subscriptions
>
> Hi,
>
> We got it by a bug today where the txn-resumer was unable to resume a
> transaction (because of a bug in the code).
>
> In less than 2 days, the txn-queue for a few documents grew to over 25k.
> We thankfully caught the problem relatively fast and were able to deal
> with it, but agents now need to process these 25k txns.
>
> If an operation fails, juju shouldn't let txn-queues grow out of control
> because of constant retries.
>
> Thanks
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> juju shouldn't let txn-queues growing out of control
>
> To manage notifications about this bug go to:
> https:/
>