Problem building

[jhonathas]

Hi everyone, I'm trying this problem here:

I've already tried using Elasticsearch with Jason and Poison and the error continues. You know what may be happening?

I completely cleared the Elasticsearch thinking there might be some duplicity, but it did not work.

The command I use is this:
mix elasticsearch.build dev-profiles --cluster V2V.ElasticsearchCluster

[danielberkompas]

@jhonathas According to the Elasticsearch docs, this should only happen when you write the same document to an index twice, while specifying the ?version parameter. The ?version querystring parameter tells Elasticsearch to reject writes if the _version field in the document is different than the one in the query string.

https://www.elastic.co/guide/en/elasticsearch/guide/current/optimistic-concurrency-control.html

Some questions that will help nail this down:

• What version of Elasticsearch are you using?
• Are you including _version in your documents? (In the Elasticsearch.Document implementations)

[jhonathas]

Hi,
My elastic search version, is: 6.5.2.

Follow print from my document.

The example of the error that I had presented was of the ProfileDocument, but since it is giving error in others also, follows print of the document. I do not use version inside.

Taking advantage, an error that gives several times and it may be that one error has connection with the other is this error here:

Thank you very much for the help

[jhonathas]

The error continues. From what I saw the error happens here -

https://github.com/danielberkompas/elasticsearch-elixir/blob/master/lib/elasticsearch/indexing/bulk.ex#L111

And when it goes from there, it gives error here -

https://github.com/danielberkompas/elasticsearch-elixir/blob/master/lib/elasticsearch/indexing/index.ex#L147

These are the 2 code locations that time out.

I tried to do this in the store:

   @impl true
   def transaction (fun) do
     {: ok, result} = Repo.transaction(fun, pool_timeout: :infinity, timeout: :infinity)
     result
   end

But it did not resolve.

I am indexing 964,000 lines from postgres.

Any idea?

[danielberkompas]

@jhonathas I'm sorry you're still experiencing this issue. Unfortunately, I don't have a clear idea what might be causing it. :-( Happy for anyone to help with this who can.