Guillaume Lederrey

@kevinconaway yes, this is most probably wrong, but also most probably of no consequence. There is a lot of ugly code there to keep backward compatibility. The Server instance created...

> > yes, this is most probably wrong, but also most probably of no consequence > > Are you sure? It will create one pool per outputwriter. If users specify...

If I read that correctly, you only return the servers for the last file that is read. It's late here, so my eyes are probably crossed. If you have a...

Well... creating duplicate OutputWriters creates so many issues that optimizing the stormpot allocator makes almost no sense before we fix them. Thanks for creating the issue, it makes the problem...

We should fix it on our side. It's not that hard to write a circuit breaker allocator. I just need to find the time... It's probably just as much effort...

The allocator thread is doing only allocations (as far as I understand the code). So blocking it is exactly what we want. We'll stop the allocation. At the moment stormpot...

Feel free to send a pull request! I don't use windows myself...

@gquintana: Maven modules are used mainly to manage dependencies. So that if someone wants a version of jmxtrans that is < 20Mb, it is possible to do. Since this OutputWriter...

In the absence of documentation, [the code always helps](https://github.com/jmxtrans/jmxtrans/blob/master/jmxtrans-output/jmxtrans-output-elastic/src/main/java/com/googlecode/jmxtrans/model/output/elastic/ElasticWriter.java#L80-L86)...

The following properties are available on the elasticsearch writer: - typeNames - booleanAsNumber - rootPrefix - connectionUrl The only one really specific to elasticsearch is `connectionUrl`, which is the URL...