# InstanceAlreadyExistsException for logstash id

**URL:** <https://discuss.elastic.co/t/instancealreadyexistsexception-for-logstash-id/163047>\
**Category:** Logstash\
**Created:** [January 5, 2019, 1:25pm UTC](https://discuss.elastic.co/t/instancealreadyexistsexception-for-logstash-id/163047 "2019-01-05T13:25:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![amitavmohanty01](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amitavmohanty01/32/58017_2.png) [@amitavmohanty01](https://discuss.elastic.co/u/amitavmohanty01)\
**Post date:** [January 5, 2019, 1:25pm UTC](https://discuss.elastic.co/t/instancealreadyexistsexception-for-logstash-id/163047/1 "2019-01-05T13:25:08Z")

</div>

I have multiple pipelines in my Logstash configuration. Each pipeline has a dedicated Kafka topic. Should the client id be same for pipelines? It seems the client id is accepted for a few but creates an InstanceAlreadyExistsException after some time.

[https://pastebin.com/xBY8H4Yv](https://pastebin.com/xBY8H4Yv) are the logs.

---

<div class="post-metadata">

**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\
**Post date:** [January 6, 2019, 3:44am UTC](https://discuss.elastic.co/t/instancealreadyexistsexception-for-logstash-id/163047/2 "2019-01-06T03:44:17Z")

</div>

The message in question is a `WARN`-level log message from the code that the Kafka Input plugin relies on.

Typically, `WARN`-level messages do not indicate a failure or a need for immediate action, but serve to act as a paper-trail when chasing down an error (which is typically logged at `ERROR`-level) or crash.

Are you experiencing an issue where one or more pipeline isn't behaving as expected?

---

<div class="post-metadata">

**Author:** ![amitavmohanty01](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amitavmohanty01/32/58017_2.png) [@amitavmohanty01](https://discuss.elastic.co/u/amitavmohanty01)\
**Post date:** [January 6, 2019, 9:40am UTC](https://discuss.elastic.co/t/instancealreadyexistsexception-for-logstash-id/163047/3 "2019-01-06T09:40:19Z")

</div>

I was trying to figure out whether this was causing any other cascaded problem. I was able to get rid of this by setting explicit client id and group id in the pipelines. I will start a different topic for the other problem.

---

<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:** [February 3, 2019, 9:40am UTC](https://discuss.elastic.co/t/instancealreadyexistsexception-for-logstash-id/163047/4 "2019-02-03T09:40:20Z")

</div>

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