# Filebat signals

**URL:** <https://discuss.elastic.co/t/filebat-signals/228670>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 18, 2020, 6:06pm UTC](https://discuss.elastic.co/t/filebat-signals/228670 "2020-04-18T18:06:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elastic\_user1](https://avatars.discourse-cdn.com/v4/letter/e/5f9b8f/32.png) [@elastic\_user1](https://discuss.elastic.co/u/elastic_user1)\
**Post date:** [April 18, 2020, 6:06pm UTC](https://discuss.elastic.co/t/filebat-signals/228670/1 "2020-04-18T18:06:26Z")

</div>

I noticed following in my log when i could not connect to Logstash logs:

```auto
    NFO pipeline/output.go:93 Attempting to reconnect to backoff(async()) with 3 reconnect attempt(s)
    NFO [publisher] pipeline/retry.go:173 retryer: send wait signal to consumer
    NFO [publisher] pipeline/retry.go:175 done
    RROR pipeline/output.go:100 Failed to connect to backoff(async()): dial tcp connect: connection refused
    NFO pipeline/output.go:93 Attempting to reconnect to backoff(async()) with 4 reconnect attempt(s)
    NFO [publisher] pipeline/retry.go:196 retryer: send unwait-signal to consumer
    NFO [publisher] pipeline/retry.go:198 done
    NFO [publisher] pipeline/retry.go:173 retryer: send wait signal to consumer
    NFO [publisher] pipeline/retry.go:175 done
    RROR pipeline/output.go:100 Failed to connect to backoff(async()): dial connect: connection refused
    NFO pipeline/output.go:93 Attempting to reconnect to backoff(async()) with 5 reconnect attempt(s)
    NFO [publisher] pipeline/retry.go:196 retryer: send unwait-signal to consumer
    NFO [publisher] pipeline/retry.go:198 done
    NFO [publisher] pipeline/retry.go:173 retryer: send wait signal to consumer
    NFO [publisher] pipeline/retry.go:175 done
    //RROR pipeline/output.go:100 Failed to connect to backoff(async()): dial tcp connect: //connection refused
    //NFO pipeline/output.go:93 Attempting to reconnect to backoff(async()) with 6 reconnect //attempt(s)
    //NFO [publisher] pipeline/retry.go:196 retryer: send unwait-signal to consumer
    //NFO [publisher] pipeline/retry.go:198 done
    //NFO [publisher] pipeline/retry.go:173 retryer: send wait signal to consumer
    //NFO [publisher] pipeline/retry.go:175 done
    //

```

I am confused, that right after an unwait signal is set, a wait signal is set at once. Why did unwait and wait signal happen?

I don't know Go, so it is not clear to me.

I examined the source code, i saw that wait and unwait signals link to SigHint()

```auto
//func (c *eventConsumer) sigWait() {
// c.wait.Store(true)
// c.sigHint()
//}

//func (c *eventConsumer) sigUnWait() {
// c.wait.Store(false)
// c.sigHint()

//func (c *eventConsumer) sigHint() {
  // send signal to unblock a consumer trying to publish events.
  // With flags being set atomically, multiple signals can be compressed into one
  // signal -> drop if queue is not empty
 // select {
 // case c.sig <- consumerSignal{tag: sigConsumerCheck}:
 // default:
 // }

```

I am not sure what sigConsumerCheck contains in my situation.

I debugged Filebeat and saw that the queue has ~2\*max\_bulk\_setting (default 2048) (in my situation it was "events":{"active":4117}}), any more events doesn't add and it is ok. Events in the queue were kept until the connect was established.  
So I didn't understand what happened when i had unwait/wait signal.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 16, 2020, 6:10pm UTC](https://discuss.elastic.co/t/filebat-signals/228670/2 "2020-05-16T18:10:45Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.