# Backoff is not reset correctly after a correct ack is sent **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [June 3, 2016, 5:22pm UTC](https://discuss.elastic.co/t/backoff-is-not-reset-correctly-after-a-correct-ack-is-sent/51816 "2016-06-03T17:22:08Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![adioss](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adioss/32/10174_2.png) [@adioss](https://discuss.elastic.co/u/adioss)\ **Post date:** [June 3, 2016, 5:22pm UTC](https://discuss.elastic.co/t/backoff-is-not-reset-correctly-after-a-correct-ack-is-sent/51816/1 "2016-06-03T17:22:08Z")
Hello! Using Filebeat v1.2.3: In case of error (no correct ACK received), filebeat retries to send the frame but before, the process is stopped during a computed duration: backoff (that is exponential until 1min) . But after an ACK is sent (no more problem) the value is not reset. So in case of new error, backoff will be probably 1min (until a filebeat reboot). Maybe we can reset backoffCount that is used to compute backoff? check: [https://github.com/adioss/beats/commit/793065013faedfaff030641988657b33c4076df4](https://github.com/adioss/beats/commit/793065013faedfaff030641988657b33c4076df4) Thanks, Adrien ---
**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\ **Post date:** [June 6, 2016, 12:55pm UTC](https://discuss.elastic.co/t/backoff-is-not-reset-correctly-after-a-correct-ack-is-sent/51816/2 "2016-06-06T12:55:14Z")
@adioss Thanks for reporting and suggesting a fix. @steffens Could you have a look at this one? ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [June 6, 2016, 1:18pm UTC](https://discuss.elastic.co/t/backoff-is-not-reset-correctly-after-a-correct-ack-is-sent/51816/3 "2016-06-06T13:18:06Z")
Thaks for reporting. Definitely a bug in 1.2.x release. Can you create an [github issue](https://github.com/elastic/beats/issues) for tracking this? Proposed change is incomplete. The variable `backoffCount` should be reset at line 135 too. Backoff behavior has been fixed/changed in master long time ago. ---
**Author:** ![adioss](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adioss/32/10174_2.png) [@adioss](https://discuss.elastic.co/u/adioss)\ **Post date:** [June 6, 2016, 3:47pm UTC](https://discuss.elastic.co/t/backoff-is-not-reset-correctly-after-a-correct-ack-is-sent/51816/4 "2016-06-06T15:47:53Z")
i've done that: [https://github.com/elastic/beats/issues/1803](https://github.com/elastic/beats/issues/1803) but i'm not allowed to change label (to put bug, filebeat and v1.2.3) and a pull request [https://github.com/elastic/beats/pull/1804](https://github.com/elastic/beats/pull/1804)). But i'm not sure it's the good process. If it's not the case (very sorry...) can you give me a feedback please? ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [June 6, 2016, 6:47pm UTC](https://discuss.elastic.co/t/backoff-is-not-reset-correctly-after-a-correct-ack-is-sent/51816/5 "2016-06-06T18:47:31Z")
Thanks for ticket plus pull request. I can set labels. But you can not set v1.2.3 as roadmap is still up to us (and 1.2.3 already being released). We might prepare for a new 1.x version soonish, so we have to wait for PR potentially going into another branch. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 24, 2016, 5:22pm UTC](https://discuss.elastic.co/t/backoff-is-not-reset-correctly-after-a-correct-ack-is-sent/51816/6 "2016-06-24T17:22:15Z")
This topic was automatically closed after 21 days. New replies are no longer allowed.