Warnings after changing logstash 5.1.1 to 5.1.2


#1

After updating from logstash 5.1.1 to 5.1.2 (also elastic) i see those messages:

{"log":"14:56:02.635 [[main]\u003eworker0] WARN logstash.outputs.elasticsearch - Failed action. {:status=\u003e409, :action=\u003e["update", {:_id=\u003e"%{id}", :_index=\u003e"ta", :_type=\u003e"events", :_routing=\u003enil, :_retry_on_conflict=\u003e1}, 2017-01-18T14:56:01.081Z %{host} %{message}], :response=\u003e{"update"=\u003e{"_index"=\u003e"ta", "_type"=\u003e"events", "_id"=\u003e"%{id}", "status"=\u003e409, "error"=\u003e{"type"=\u003e"version_conflict_engine_exception", "reason"=\u003e"[events][%{id}]: version conflict, current version [453] is different than the one provided [452]", "index_uuid"=\u003e"iomvsETXQVezDOCweq2gLQ", "shard"=\u003e"0", "index"=\u003e"ta"}}}}\n","stream":"stdout","time":"2017-01-18T14:56:02.645718181Z"}
...

How to fix this or this is normal?
My data is updated by sheduler form sql database.


(Jymit Singh Khondhu) #2

Hi, how did you move forward with the upgrade from LS 5.1.1 to 5.1.2? Are they still in the same location on the file system?


#3

New versions (elastic + logstash) is a clean installation to new clean docker instance.
Configuration is old. For example:

jdbc {
jdbc_connection_string => "jdbc:postgresql://..."
jdbc_user => "postgres"
jdbc_password => "pass"
jdbc_driver_library => "/connectors/postgresql-9.4.1212.jar"
jdbc_driver_class => "org.postgresql.Driver"
schedule => "*/7 * * * *"
statement => "SELECT id, name, updated_at::varchar, created_at::varchar FROM sale_types"
type => "sale_types"
}

..
output {
elasticsearch {
index => "ta"
document_type => "%{type}"
hosts => ["http://elastic:9200"]
doc_as_upsert => true
action => "update"
document_id => "%{id}"
}
}


(Jymit Singh Khondhu) #4

How is[quote="tbw, post:1, topic:72030"]
"reason"=\u003e"[events][%{id}]: version conflict, current version [453] is different than the one provided [452]"
[/quote]

The document_id is the current cause for concern. Is this a clean installation with no indices at all?


#5

yes this is clean installation, also after delete index and recreating them warnings is repeating
Also this warnings for < 1% of all records


#6

Now i think it is becouse i set 2 cores processor for docker. Before i was use 1 cpu configuration.
Is this a bug?


(system) #7

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