# Why do we see too many logs for the visibility-queue-processor

**URL:** <https://community.temporal.io/t/why-do-we-see-too-many-logs-for-the-visibility-queue-processor/7595>\
**Category:** Community Support\
**Created:** [March 16, 2023, 5:42pm UTC](https://community.temporal.io/t/why-do-we-see-too-many-logs-for-the-visibility-queue-processor/7595 "2023-03-16T17:42:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kenand](https://avatars.discourse-cdn.com/v4/letter/k/8dc957/32.png) [@kenand](https://community.temporal.io/u/kenand)\
**Post date:** [March 16, 2023, 5:42pm UTC](https://community.temporal.io/t/why-do-we-see-too-many-logs-for-the-visibility-queue-processor/7595/1 "2023-03-16T17:42:26Z")

</div>

Hello

We see thousands of below logs with our temporal cluster. To be precise 11K logs for 10 seconds.

```
{"level":"info","ts":"2023-03-16T16:21:29.999Z","msg":"queue reader started","shard-id":467" component":"visibility-queue-processor","queue-reader-id":0,"lifecycle":"Started","logging-call-at":"reader.go:166"}

{"level":"info","ts":"2023-03-16T16:21:29.999Z","msg":"queue reader stopped","shard-id":5353, "component":"timer-queue-processor","queue-reader-id":0,"lifecycle":"Stopped","logging-call-at":"reader.go:184"}

```

The question is; is this something that we need to be concerned? May it explain some of the performance issues we have with our temporal deployment.

We are on server version: 1.18.5  
And our cluster is backed by Aurora RDS.

---

<div class="post-metadata">

**Author:** ![Ci-Ci\_Thomson](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/ci-ci_thomson/32/3512_2.png) [@Ci-Ci\_Thomson](https://community.temporal.io/u/Ci-Ci_Thomson)\
**Post date:** [March 21, 2023, 7:21pm UTC](https://community.temporal.io/t/why-do-we-see-too-many-logs-for-the-visibility-queue-processor/7595/2 "2023-03-21T19:21:43Z")

</div>

Hi Kenand,  
This issue is fixed in server version 1.19. You will still see the logs on service start up, which is for showing the background task processing for a certain queue is started (for each shard).
