# Default schedule logstash (issue with indexing to Elasticsearch)

**URL:** <https://discuss.elastic.co/t/default-schedule-logstash-issue-with-indexing-to-elasticsearch/107196>\
**Category:** Logstash\
**Created:** [November 10, 2017, 1:59pm UTC](https://discuss.elastic.co/t/default-schedule-logstash-issue-with-indexing-to-elasticsearch/107196 "2017-11-10T13:59:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![malhotras](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@malhotras](https://discuss.elastic.co/u/malhotras)\
**Post date:** [November 10, 2017, 1:59pm UTC](https://discuss.elastic.co/t/default-schedule-logstash-issue-with-indexing-to-elasticsearch/107196/1 "2017-11-10T13:59:51Z")

</div>

I am facing problem with Indexing data to Elasticsearch using logstash. I noticed that Logstash is scheduled to restart changing process id after certain point of time. This is creating problem with indexing data to the Elasticsearch.

# systemctl status logstash

```
  Nov 10 13:04:03 logstash01-test logstash[8612]: {"stk_id":null,"wrmg":"ja}
  root@logstash01-test 20171110-13:04:15 /etc/logstash/conf.d

```

# systemctl status logstash

```
● logstash.service - logstash
   Loaded: loaded (/etc/systemd/system/logstash.service; disabled)
   Active: active (running) since Fri 2017-11-10 13:04:16 CET; 2s ago
    Main PID: 8674 (java)
    CGroup: /system.slice/logstash.service
     └─8674 /usr/bin/java -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75
  -XX:+UseCMSInitiatingOccupancyOnly -XX:+DisableExplicitGC -Djava.awt.headless=true -Dfile.encoding=UTF-8 -XX:+HeapDumpOnOutOfMemoryError -Xmx5g -Xms1g -Xss2048k -Djffi.boot.library.path=/usr/share/logsta...

 Nov 10 13:04:16 logstash01-test systemd[1]: logstash.service holdoff time over, scheduling restart.
 Nov 10 13:04:16 logstash01-test systemd[1]: Stopping logstash...
 Nov 10 13:04:16 logstash01-test systemd[1]: Starting logstash...
 Nov 10 13:04:16 logstash01-test systemd[1]: Started logstash.
root@logstash01-test 20171110-13:04:24 /etc/logstash/conf.d

```

# systemctl status logstash

```
  ● logstash.service - logstash
    Loaded: loaded (/etc/systemd/system/logstash.service; disabled)
  Active: active (running) since Fri 2017-11-10 13:04:16 CET; 20s ago
 Main PID: 8674 (java)
 CGroup: /system.slice/logstash.service
 └─8674 /usr/bin/java -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75

 -XX:+UseCMSInitiatingOccupancyOnly -XX:+DisableExplicitGC -Djava.awt.headless=true -Dfile.encoding=UTF-8 -XX:+HeapDumpOnOutOfMemoryError -Xmx5g -Xms1g -Xss2048k -Djffi.boot.library.path=/usr/share/logsta...

  Nov 10 13:04:36 logstash01-test logstash[8674]: {"stk_id":null,"w":"u"}

```

I have no scheduling set-up in my logstash conf file. Is it happening by default?

```
 jdbc {
            jdbc_connection_string => "jdbc:informix-sqli://informix:1500/star:INFORMIXSERVER=test"
            jdbc_user => "star"
            jdbc_password => " ****"
            jdbc_driver_library => "/etc/logstash/lib/ifxjdbc-3-50-JC7.jar"
            jdbc_driver_class => "com.informix.jdbc.IfxDriver"
            jdbc_fetch_size => "5000000"
            statment => "select * from start"
 }

```

Any suggestions??

---

<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:** [December 8, 2017, 2:00pm UTC](https://discuss.elastic.co/t/default-schedule-logstash-issue-with-indexing-to-elasticsearch/107196/2 "2017-12-08T14:00:20Z")

</div>

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