# Start warinnig **URL:** \ **Category:** Logstash\ **Created:** [March 20, 2018, 6:28am UTC](https://discuss.elastic.co/t/start-warinnig/124692 "2018-03-20T06:28:00Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [March 20, 2018, 6:28am UTC](https://discuss.elastic.co/t/start-warinnig/124692/1 "2018-03-20T06:28:01Z")
[2018-03-20T14:25:23,077][INFO][logstash.pipeline] Starting pipeline {"id"=\>"main", "pipeline.workers"=\>16, "pipeline.batch.size"=\>12500, "pipeline.batch.delay"=\>5, " **pipeline.max\_inflight"=\>200000** } [2018-03-20T14:25:23,078][WARN][logstash.pipeline] **CAUTION: Recommended inflight events max exceeded! Logstash will run with up to 200000 events in memory in your current configuration. If your message sizes are large this may cause instability with the default heap size. Please consider setting a non-standard heap size, changing the batch size (currently 12500), or changing the number of pipeline workers (currently 16)** how to change the **pipeline.max\_inflight"=\>200000** it big than "pipeline.batch.size"=\>12500, how i can do it ? thanks. ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [March 20, 2018, 6:31am UTC](https://discuss.elastic.co/t/start-warinnig/124692/2 "2018-03-20T06:31:31Z")
I don't understand what you're asking. Logstash warns about `pipeline.max_inflight` for a reason. Why are you setting it so high? It's most likely a bad idea. ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [March 20, 2018, 6:33am UTC](https://discuss.elastic.co/t/start-warinnig/124692/3 "2018-03-20T06:33:24Z")
**pipeline.max\_inflight** this i don't setting . it auto output . i wan't to know how to change it **pipeline.max\_inflight** to small. thanks. logstash is 5.6.8 ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [March 20, 2018, 6:36am UTC](https://discuss.elastic.co/t/start-warinnig/124692/4 "2018-03-20T06:36:21Z")
in logstash.yml i only setting this: ``` pipeline.batch.size: 12500 pipeline.batch.delay: 5 queue.max_events: 12500 ``` but when start logstash the **pipeline.max\_inflight** is output a warning. ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [March 20, 2018, 5:58pm UTC](https://discuss.elastic.co/t/start-warinnig/124692/5 "2018-03-20T17:58:19Z")
Okay. I think pipeline.max\_inflight is computed based on the batch size and the number of pipeline workers. You have 16 CPU cores, right? Or you've otherwise configured Logstash to have 16 pipeline workers. 200,000 / 12,500 = 16. ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [March 21, 2018, 12:43am UTC](https://discuss.elastic.co/t/start-warinnig/124692/6 "2018-03-21T00:43:19Z")
ok i change the pipe work and try thanks. ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [March 21, 2018, 12:46am UTC](https://discuss.elastic.co/t/start-warinnig/124692/7 "2018-03-21T00:46:07Z")
i add the workers in logstash the warning is also. ``` [2018-03-21T08:44:35,443][INFO][logstash.pipeline] Starting pipeline {"id"=>"main", "pipeline.workers"=>16, "pipeline.batch.size"=>12500, "pipeline.batch.delay"=>5, "pipeline.max_inflight"=>200000} [2018-03-21T08:44:35,443][WARN][logstash.pipeline] CAUTION: Recommended inflight events max exceeded! Logstash will run with up to 200000 events in memory in your current configuration. If your message sizes are large this may cause instability with the default heap size. Please consider setting a non-standard heap size, changing the batch size (currently 12500), or changing the number of pipeline workers (currently 16) ``` ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [March 21, 2018, 8:11pm UTC](https://discuss.elastic.co/t/start-warinnig/124692/8 "2018-03-21T20:11:00Z")
??? You still have 16 pipeline workers so with a 12500 batch size the inflight event max is still 200k. ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [March 22, 2018, 12:33am UTC](https://discuss.elastic.co/t/start-warinnig/124692/9 "2018-03-22T00:33:17Z")
how can do it ? can't setting pipeline.batch.size: 12500 in logstash? ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [March 22, 2018, 6:55am UTC](https://discuss.elastic.co/t/start-warinnig/124692/10 "2018-03-22T06:55:58Z")
Reduce the batch size and/or the number of pipeline workers: [https://www.elastic.co/guide/en/logstash/current/logstash-settings-file.html](https://www.elastic.co/guide/en/logstash/current/logstash-settings-file.html) Or, live with the warning and its consequences. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 19, 2018, 6:56am UTC](https://discuss.elastic.co/t/start-warinnig/124692/11 "2018-04-19T06:56:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.