Scheduling and Retries

Fluent Bit has an Engine that helps to coordinate the data ingestion from input plugins and calls the Scheduler to decide when it is time to flush the data through one or multiple output plugins. The Scheduler flushes new data at a fixed time of seconds and the Scheduler retries when asked.
Once an output plugin gets called to flush some data, after processing that data it can notify the Engine three possible return statuses:
  • OK
  • Retry
  • Error
If the return status was OK, it means it was successfully able to process and flush the data, if it returned an Error status, means that an unrecoverable error happened and the engine should not try to flush that data again. If a Retry was requested, the Engine will ask the Scheduler to retry to flush that data, the Scheduler will decide how many seconds to wait before that happens.

Configuring Retries

The Scheduler provides a simple configuration option called Retry_Limit which can be set independently on each output section. This option allows to disable retries or impose a limit to try N times and then discard the data after reaching that limit:
Integer value to set the maximum number of retries allowed. N must be >= 1 (default: 1)
no_limits or False
When Retry_Limit is set to no_limits orFalse, means that there is not limit for the number of retries that the Scheduler can do.
When Retry_Limit is set to no_retries, means that reries are disabled and Scheduler would not try to send data to the destination if it failed the first time.


The following example configures two outputs where the HTTP plugin has an unlimited number of while the Elasticsearch plugin have a limit of 5 retries:
Name http
Port 8080
Retry_Limit False
Name es
Port 9200
Logstash_Format On
Retry_Limit 5