Commit graph

15 commits

Author SHA1 Message Date
Mattias Appelgren
4af3f86a05 config/logstash.yml: Remove trailing whitespace
Fixes #6635
2017-02-13 06:17:57 -05:00
Suyog Rao
fbfcf7ceaa specify max_events relation as well
Fixes #6343
2016-12-01 20:13:52 -05:00
Suyog Rao
89c4c4fe49 Add default setting for queue.max_bytes
Fixes #6343
2016-12-01 20:13:51 -05:00
Colin Surprenant
38fc84b367 add support for queue.checkpoint.{acks|writes} settings
add queue.max_acked_checkpoint and queue.checkpoint_rate settings

now using checkpoint.max_acks, checkpoint.max_writes and checkpoint.max_interval

rename options

wip rework checkpointing

refactored full acked pages handling on acking and recovery

correclty close queue

proper queue open/recovery

checkpoint dump utility

checkpoint on writes

removed debug code and added missing newline

added better comment on contiguous checkpoints

fix spec for new pipeline setting
2016-11-22 15:55:32 -05:00
Colin Surprenant
ab05082a89 merge feature/java_persistence into 5.x 2016-10-31 17:03:40 -04:00
Tal Levy
224bc36a27 remove commented value for path.logs in default settings file
the build scripts rely on the value not being present to update with
appropriate value for the package

Fixes #5904
2016-09-13 18:43:04 -04:00
Tal Levy
9c687a37c4 Set default log.level to INFO
sets default to INFO and updates some verbose logging to
more appropriate, less verbose log levels where it makes sense.

Closes #5735.
Closes #5893.

Fixes #5898
2016-09-13 16:43:20 -04:00
Tal Levy
ce68fb4706 update path.log to path.logs directory, and respect it in log4j2
Fixes #5876
2016-09-08 18:10:02 -04:00
Tal Levy
b545b83390 Migrate Logstash to Log4j2 Logging (#5651)
Migrate to use Log4j2 for Logstash logging
2016-08-26 18:11:22 +00:00
Pier-Hugues Pellerin
c7f6cba5c8 --http.port Now accept a port range
This PR does a few modifications for our webserver:
 - Add a PortRange setting type.
 - allow the --http.port option to accept a port range or a single port, when a range is provided Logstash will incrementally try this list to find a free port for the webserver.
 - Logstash will report in the log which port it is using. (INFO LEVEL)
 - It refactors a few methods of the webserver.
 - It adds test for the binding of the ports.

Notes:

Port range can be defined in the logstash.yml or pass via the command line like this.

 `bin/logstash -e 'input { generator {}} output { null {}}' --log.level verbose --http.port 2000-2005`

Fixes #5774
2016-08-19 08:04:01 -04:00
DeDe Morton
51083d4666 corrected description of pipeline.batch.delay from seconds to ms
Fixes #5738
2016-08-08 13:54:34 -04:00
Joao Duarte
c03c5523a3 add data.path setting
Fixes #5528
2016-06-24 07:32:25 -04:00
DeDe Morton
c5fe902e66 Fixes from the review
Fixes #5332
2016-05-23 17:02:28 +00:00
Suyog Rao
43fde411bd Corrections to CLI options
Fixes #5331
2016-05-20 00:24:09 +00:00
Joao Duarte
3a6b1dafaa introduce yaml settings file and cli long switches
* by default lives in LOGSTASH_HOME/config/logstash.yml
* location can be changed by $LS_SETTINGS_DIR or --path.settings
* overrides defaults of LogStash::Environment, BUT
* CLI flags override the yaml file
* several breaking changes to cli flag names (see config/logstash.yml)
* setting values are now type checked (see Setting and Settings classes)

Fixes #5313
2016-05-19 19:20:37 +01:00