# Logstash -Using Schedular with JDBC Input plugin results in Ram being locked for scheduler and high CPU usage

**URL:** <https://discuss.elastic.co/t/logstash-using-schedular-with-jdbc-input-plugin-results-in-ram-being-locked-for-scheduler-and-high-cpu-usage/53200>\
**Category:** Logstash\
**Created:** [June 18, 2016, 3:33am UTC](https://discuss.elastic.co/t/logstash-using-schedular-with-jdbc-input-plugin-results-in-ram-being-locked-for-scheduler-and-high-cpu-usage/53200 "2016-06-18T03:33:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![amitpalsaluja](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@amitpalsaluja](https://discuss.elastic.co/u/amitpalsaluja)\
**Post date:** [June 18, 2016, 3:33am UTC](https://discuss.elastic.co/t/logstash-using-schedular-with-jdbc-input-plugin-results-in-ram-being-locked-for-scheduler-and-high-cpu-usage/53200/1 "2016-06-18T03:33:32Z")

</div>

Hi ,  
Using JDBC Input plugin with Schedule option , results in  
a. RAM(around 150+ MB) being Locked for the process.  
b. High CPU Usage.

## Version details

1. logstash-2.2.0

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [June 18, 2016, 10:13am UTC](https://discuss.elastic.co/t/logstash-using-schedular-with-jdbc-input-plugin-results-in-ram-being-locked-for-scheduler-and-high-cpu-usage/53200/2 "2016-06-18T10:13:49Z")

</div>

What does your configuration look like?

---

<div class="post-metadata">

**Author:** ![amitpalsaluja](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@amitpalsaluja](https://discuss.elastic.co/u/amitpalsaluja)\
**Post date:** [June 19, 2016, 1:41pm UTC](https://discuss.elastic.co/t/logstash-using-schedular-with-jdbc-input-plugin-results-in-ram-being-locked-for-scheduler-and-high-cpu-usage/53200/3 "2016-06-19T13:41:11Z")

</div>

here it goes-

input{

```
	jdbc {
		  
			jdbc_driver_library => "<path to jar dolder>/ojdbc6-11.2.0.3.0.jar"
			jdbc_driver_class => "Java::oracle.jdbc.driver.OracleDriver"
			jdbc_connection_string => "jdbc:oracle:thin:@<oracle db ip>:<oracle db port>/<db service_name>"
			jdbc_user => "<user name>"
			jdbc_password => "<password>"
            schedule => "0 0/20 * * * ?"
			statement => "select ID as	id	,name as person name from person	"
	 }

```

}

filter{

```
mutate{
convert =>{"id" => "integer"}

```

}  
// mutate a few other columns needed as per business case

}

output {  
#stdout{ codec =\> json\_lines}  
elasticsearch {  
hosts =\> [":"]  
action =\> "index"  
index =\> "person\_details"  
document\_type =\> "person\_details"  
document\_id =\> "%{id}"  
}  
}

---

<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:** [July 6, 2017, 4:52am UTC](https://discuss.elastic.co/t/logstash-using-schedular-with-jdbc-input-plugin-results-in-ram-being-locked-for-scheduler-and-high-cpu-usage/53200/4 "2017-07-06T04:52:02Z")

</div>