Hi, right now we do have an issue with the ElasticSearch Rest appender when using a an amazon based ES instance.
this results in two rather stange effects I'd like to discuss 1) we do get an Exception by DS (SCR) that it's not able to obtain a lock on a service ... don't know where this is coming from. [1] 2) The configured service endpoints [2] vanishes [3] and the rest appender isn't capable of finding the ES endpoint configured in the service config. I have one suspicion, that the discovery for other endpoints is enabled cause we do see some sort of "CHECKER" thread [4] running ... therefore I opened issue KARAF-4794 and am planning on disabling this by default. regards, Achim [1] - https://gist.github.com/ANierbeck/bfcad89716b04b6beea8a409ee278545#file-elasticsearch-rest-appender-L4-L29 [2] - https://gist.github.com/ANierbeck/bfcad89716b04b6beea8a409ee278545#file-elasticsearch-rest-appender-L1 [3] - https://gist.github.com/ANierbeck/bfcad89716b04b6beea8a409ee278545#file-elasticsearch-rest-appender-L60 [4] - https://gist.github.com/ANierbeck/bfcad89716b04b6beea8a409ee278545#file-elasticsearch-rest-appender-L60-L61 [5] - https://issues.apache.org/jira/browse/KARAF-4794 -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
