v0.5.2

This release adds two additional flags for seastat server to control the maximum number of requests to Jolokia at any one time (concurrency) and maximum duration before a Jolokia request times out (timeout)

If you find Jolokia getting stuck and timing out, consider tuning down the concurrency parameter (which control
the maximum number of Jolokia requests in flight at any one time).

$ ./seastat server -p 8080 --concurrency 2

I've found 10 to be a good middleground for a Cassandra instance running on a beefy machine (8+ cores and 32GB of heap space) but your experience may vary.

We also expose a flag to configure the default Jolokia timeout per request (which you can use in combination with any other flags)

$ ./seastat server -p 8080 --timeout 2s
$ ./seastat server -p 8080 --concurrency=5 --timeout 2s

It is recommended to not set the timeout too high. A high timeout indicates Jolokia struggling to serve all the metrics needed.