# Op\_type=create; log filling with "document already exists" exceptions

**URL:** https://discuss.elastic.co/t/op-type-create-log-filling-with-document-already-exists-exceptions/6435
**Category:** Elasticsearch
**Created:** [January 18, 2012, 11:26pm UTC](https://discuss.elastic.co/t/op-type-create-log-filling-with-document-already-exists-exceptions/6435 "2012-01-18T23:26:27Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![drew\_letcher](https://avatars.discourse-cdn.com/v4/letter/d/b3f665/32.png) [@drew\_letcher](https://discuss.elastic.co/u/drew_letcher)
#### Post date: [January 18, 2012, 11:26pm UTC](https://discuss.elastic.co/t/op-type-create-log-filling-with-document-already-exists-exceptions/6435/1 "2012-01-18T23:26:27Z")

</div>

Is there any way to keep this exception from being logged?

For redudancy we have two importers indexing the same document  
stream. We use op\_type=create to make sure only one succeeds. This  
"document already exists" is a normal condition for us. It fills up  
the log and makes it hard to find other errors.

Thanks,  
Drew

---

<div class="post-metadata">

### Author: ![drew\_letcher](https://avatars.discourse-cdn.com/v4/letter/d/b3f665/32.png) [@drew\_letcher](https://discuss.elastic.co/u/drew_letcher)
#### Post date: [January 18, 2012, 11:40pm UTC](https://discuss.elastic.co/t/op-type-create-log-filling-with-document-already-exists-exceptions/6435/2 "2012-01-18T23:40:15Z")

</div>

I think I figured this out.

The log4j setting is action: DEBUG

The log entries start with [time][DEBUG][action.index]

If I set the log4j to action: INFO I assume these errors won't be  
logged.

---

<div class="post-metadata">

### Author: ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [January 19, 2012, 7:17am UTC](https://discuss.elastic.co/t/op-type-create-log-filling-with-document-already-exists-exceptions/6435/3 "2012-01-19T07:17:53Z")

</div>

Its no longer logged under DEBUG (version conflict failures) in master.

On Thu, Jan 19, 2012 at 1:40 AM, drew.letcher \<  
[drew.letcher@interactivedata.com](mailto:drew.letcher@interactivedata.com)\> wrote:

> I think I figured this out.
> 
> The log4j setting is action: DEBUG
> 
> The log entries start with [time][DEBUG][action.index]
> 
> If I set the log4j to action: INFO I assume these errors won't be  
> logged.

---

<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, 3:42am UTC](https://discuss.elastic.co/t/op-type-create-log-filling-with-document-already-exists-exceptions/6435/4 "2017-07-06T03:42:10Z")

</div>