# ParNew and ConcurrentMarkSweep seen in logs

**URL:** <https://discuss.elastic.co/t/parnew-and-concurrentmarksweep-seen-in-logs/288806>\
**Category:** Logstash\
**Created:** [November 9, 2021, 6:30pm UTC](https://discuss.elastic.co/t/parnew-and-concurrentmarksweep-seen-in-logs/288806 "2021-11-09T18:30:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MKirby](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@MKirby](https://discuss.elastic.co/u/MKirby)\
**Post date:** [November 9, 2021, 6:30pm UTC](https://discuss.elastic.co/t/parnew-and-concurrentmarksweep-seen-in-logs/288806/1 "2021-11-09T18:30:30Z")

</div>

Good Afternoon everyone;

I am seeing the following lines when I place my Logstash in Debug mode to collect logs. I have a feeling that it is what is stopping me from seeing any syslog that has been forwarded to the logstash.

```auto
system.syslog
[2021-11-09T13:05:46,805][DEBUG][logstash.outputs.file][main] Starting flush cycle
13:05:46.000
system.syslog
[2021-11-09T13:05:46,950][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}
13:05:46.000
system.syslog
[2021-11-09T13:05:46,950][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}
13:05:46.805
logstash.log
[logstash.log][DEBUG] Starting flush cycle
13:05:46.950
logstash.log
[logstash.log][DEBUG] collector name {:name=>"ParNew"}
13:05:46.950
logstash.log
[logstash.log][DEBUG] collector name {:name=>"ConcurrentMarkSweep"}
13:05:48.000
system.syslog
[2021-11-09T13:05:48,806][DEBUG][logstash.outputs.file][main] Starting flush cycle
13:05:48.806
logstash.log
[logstash.log][DEBUG] Starting flush cycle
13:05:49.000
system.syslog
[2021-11-09T13:05:49,687][DEBUG][org.logstash.execution.PeriodicFlush][main] Pushing flush onto pipeline.

```

If this is bad, what steps would I take to remove it?  
Thank you for your assistance.

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [November 9, 2021, 7:31pm UTC](https://discuss.elastic.co/t/parnew-and-concurrentmarksweep-seen-in-logs/288806/2 "2021-11-09T19:31:07Z")

</div>

This is normal. Personally I would prefer most of those message be TRACE rather than DEBUG.

---

<div class="post-metadata">

**Author:** ![MKirby](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@MKirby](https://discuss.elastic.co/u/MKirby)\
**Post date:** [November 9, 2021, 7:33pm UTC](https://discuss.elastic.co/t/parnew-and-concurrentmarksweep-seen-in-logs/288806/3 "2021-11-09T19:33:05Z")

</div>

Thank you Badger for the input. So seeing multiple "ParNew" and "ConcurrentMarkSweep" lines per minute is normal and should not be worrisome?

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [November 9, 2021, 7:36pm UTC](https://discuss.elastic.co/t/parnew-and-concurrentmarksweep-seen-in-logs/288806/4 "2021-11-09T19:36:20Z")

</div>

That is correct.

---

<div class="post-metadata">

**Author:** ![MKirby](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@MKirby](https://discuss.elastic.co/u/MKirby)\
**Post date:** [November 9, 2021, 7:37pm UTC](https://discuss.elastic.co/t/parnew-and-concurrentmarksweep-seen-in-logs/288806/5 "2021-11-09T19:37:22Z")

</div>

Thank you. We can close this question then.

---

<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 7, 2021, 7:38pm UTC](https://discuss.elastic.co/t/parnew-and-concurrentmarksweep-seen-in-logs/288806/6 "2021-12-07T19:38:14Z")

</div>

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