Rene Lengwinat
Rene Lengwinat
@bechtoldt any thoughts on this?
We've just shipped version 0.4.3. Can you retest your scenario with this release?
Should be fixed in 0.4.3. Can you retest this scenario?
Strange thing. I've used parallel tests with more than 30 scenarios and did not experience any issue. I will try to reproduce it on my machine. thanks for reporting
Hi Kelvin, glad you're sticking with this. Your hiera version looks pretty old. 1.3.4 was released in 2014, current is 3.0.6. Any chance you can update to a more current...
Should be fixed in 0.4.3. Can you retest this scenario?
+1 for this feature I think it wouldn't be hard to implement a simple user-management using redis or another "light" storage solution, once you got there adding and sharing "saved...
I must agree that the idea of using the already present ElasticSearch as storage is tempting, but in my opinion it is not clever to use the logstash "data sink"...
Again, it's tempting but lets assume the typical setup. There are shipper nodes and the indexer which are assembled in the preferred way: node1:[logstash-shipper] -> node2:[(redis|messagebroker) ~> logstash-indexer -> elasticsearch]...