# Pulling data from SQL server main pipeline stalls

**URL:** https://discuss.elastic.co/t/pulling-data-from-sql-server-main-pipeline-stalls/85307
**Category:** Logstash
**Created:** [May 10, 2017, 9:01pm UTC](https://discuss.elastic.co/t/pulling-data-from-sql-server-main-pipeline-stalls/85307 "2017-05-10T21:01:32Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![cogdellj](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@cogdellj](https://discuss.elastic.co/u/cogdellj)
#### Post date: [May 10, 2017, 9:01pm UTC](https://discuss.elastic.co/t/pulling-data-from-sql-server-main-pipeline-stalls/85307/1 "2017-05-10T21:01:32Z")

</div>

I wrote a simple sql query to get test data it pulls the top 100 with no problem when I tried to remove the top 100 and pull in the 2500 records in the table logstash shutsdown after a few seconds with the following from the error log:  
[2017-05-09T14:10:03,376][INFO][logstash.outputs.elasticsearch] New Elasticsearch output {:class=\>"LogStash::Outputs::ElasticSearch", :hosts=\>[#\<URI::HTTP:0x3fe240a URL:[http://localhost:9200](http://localhost:9200)\>]}  
[2017-05-09T14:10:03,376][INFO][logstash.pipeline] Starting pipeline {"id"=\>"main", "pipeline.workers"=\>16, "pipeline.batch.size"=\>125, "pipeline.batch.delay"=\>5, "pipeline.max\_inflight"=\>2000}  
[2017-05-09T14:10:04,078][INFO][logstash.pipeline] Pipeline main started  
[2017-05-09T14:10:04,141][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=\>9600}  
[2017-05-09T14:10:04,172][INFO][logstash.inputs.jdbc] (0.062000s) select Employee\_id,last\_name,First\_Name,title,DepartmentID from dbo.employee  
[2017-05-09T14:10:09,164][WARN][logstash.agent] stopping pipeline {:id=\>"main"}  
[2017-05-09T14:10:14,203][WARN][logstash.shutdownwatcher] {"inflight\_count"=\>1071, "stalling\_thread\_info"=\>{"other"=\>[{"thread\_id"=\>30, "name"=\>"[main]\>worker0", "current\_call"=\>"[...]/logstash-core/lib/logstash/output\_delegator\_strategies/single.rb:14:in `synchronize'"}, {"thread_id"=>31, "name"=>"[main]>worker1", "current_call"=>"[...]/logstash-core/lib/logstash/output_delegator_strategies/single.rb:14:in`synchronize'"}, {"thread\_id"=\>34, "name"=\>"[main]\>worker4", "current\_call"=\>"[...]/vendor/bundle/jruby/1.9/gems/awesome\_print-1.7.0/lib/awesome\_print/inspector.rb:126:in `tty?'"}, {"thread_id"=>35, "name"=>"[main]>worker5", "current_call"=>"[...]/logstash-core/lib/logstash/output_delegator_strategies/single.rb:14:in`synchronize'"}, {"thread\_id"=\>36, "name"=\>"[main]\>worker6", "current\_call"=\>"[...]/logstash-core/lib/logstash/output\_delegator\_strategies/single.rb:14:in `synchronize'"}, {"thread_id"=>38, "name"=>"[main]>worker8", "current_call"=>"[...]/logstash-core/lib/logstash/output_delegator_strategies/single.rb:14:in`synchronize'"}, {"thread\_id"=\>39, "name"=\>"[main]\>worker9", "current\_call"=\>"[...]/logstash-core/lib/logstash/output\_delegator\_strategies/single.rb:14:in `synchronize'"}, {"thread_id"=>40, "name"=>"[main]>worker10", "current_call"=>"[...]/logstash-core/lib/logstash/output_delegator_strategies/single.rb:14:in`synchronize'"}, {"thread\_id"=\>43, "name"=\>"[main]\>worker13", "current\_call"=\>"[...]/logstash-core/lib/logstash/output\_delegator\_strategies/single.rb:14:in `synchronize'"}]}} [2017-05-09T14:10:19,179][WARN][logstash.shutdownwatcher] {"inflight_count"=>321, "stalling_thread_info"=>{"other"=>[{"thread_id"=>35, "name"=>"[main]>worker5", "current_call"=>"[...]/vendor/bundle/jruby/1.9/gems/awesome_print-1.7.0/lib/awesome_print/inspector.rb:156:in`printable'"}, {"thread\_id"=\>38, "name"=\>"[main]\>worker8", "current\_call"=\>"[...]/logstash-core/lib/logstash/output\_delegator\_strategies/single.rb:14:in `synchronize'"}, {"thread_id"=>40, "name"=>"[main]>worker10", "current_call"=>"[...]/logstash-core/lib/logstash/output_delegator_strategies/single.rb:14:in`synchronize'"}]}}

I am not sure what to change in the logstash.yml to prevent this from happening the box its on has 16 cpus and 96GB of ram so I don't think its the resources.

---

<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: [June 7, 2017, 9:08pm UTC](https://discuss.elastic.co/t/pulling-data-from-sql-server-main-pipeline-stalls/85307/2 "2017-06-07T21:08:30Z")

</div>

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