Remove queue.checkpoint.interval from docs

Fixes #8927
This commit is contained in:
DeDe Morton 2018-01-10 09:21:45 -08:00
parent 3ee8255f88
commit 71f6b362ec
2 changed files with 0 additions and 12 deletions

View file

@ -150,14 +150,6 @@ When recording a checkpoint, Logstash will:
* Call fsync on the head page.
* Atomically write to disk the current state of the queue.
// REVIEWERS: I've removed the descriptions of these options here because it
// sounds like users are confused about when to change these settings. The
// settings are already described in the reference topic about the logstash.yml.
// I've also removed the statement about tuning queue.checkpoint.writes to
// higher and lower values because it sounds like most users should either
// accept the default or set the option to 1.
The process of checkpointing is atomic, which means any update to the file is saved if successful.
If Logstash is terminated, or if there is a hardware-level failure, any data

View file

@ -174,10 +174,6 @@ The `logstash.yml` file includes the following settings:
| The maximum number of written events before forcing a checkpoint when persistent queues are enabled (`queue.type: persisted`). Specify `queue.checkpoint.writes: 0` to set this value to unlimited.
| 1024
| `queue.checkpoint.interval`
| The interval in milliseconds when a checkpoint is forced on the head page when persistent queues are enabled (`queue.type: persisted`). Specify `queue.checkpoint.interval: 0` for no periodic checkpoint.
| 1000
| `queue.drain`
| When enabled, Logstash waits until the persistent queue is drained before shutting down.
| false