Create return 409 on non conflict items


(Ted Kyungtae Kim) #1

We are storing data from wearable devices to ES, and having a weird situation here.

We are 'create'ing the document and we are getting 409(DocumentAlreadyExistsException) when there isn't any existing document at all.

I'm wondering if we can handle issue.

Thanks in advance.


(David Pilato) #2

How do you index your documents?
Which exact call?


(Ted Kyungtae Kim) #3

@dadoonet thanks for the quick response... we used bulk API as below

{"create":{"_index":"sleepdata","_type":"n1-njsmnfee1f3oh72zg","_id":1447186076}}
 {"start":"2015-11-10T20:07:56.000Z","end":"2015-11-10T22:58:56.000Z","startIndex":585,"endIndex":761,"info":{"graph":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0],"restlessCount":3,"wakeupCount":0,"averageDiff":2.0760233918128654,"totalTime":171,"totalBadTime":9,"deepMinute":6},"oldstart":"2015-11-10T20:02:56.000Z","oldEnd":"2015-11-10T22:58:56.000Z","id":1447186076,"startUnix":1447186076,"endUnix":1447196336}

We are certain that the id is not been created before.


(David Pilato) #4

Try GET sleepdata/n1-njsmnfee1f3oh72zg/1447186076


(Ted Kyungtae Kim) #5

GET sleepdata/n1-njsmnfee1f3oh72zg/1447186076

It give us nothing :frowning: We have looked pretty deeply, but couldn't find the reason. I know there are options on partial update retry_on_conflict, and I'm wondering if we can apply the same to 'create'.

This is not happening every single time, rather sporadically. We usually bulk several thousands documents to different index before we send the api. If that helps to understand better.

We are using ES 1.7.


(system) #6