I'm trying to get a lot more visibility and metrics into what's going on
under the hood.
Occasionally, we see spikes in memory. I'd like to get heap mem used on a
per shard basis. If I'm not mistaken, somewhere somehow, this Lucene index
that is a shard is using memory in the heap, and I'd like to collect metric.
It may also be an operation somewhere higher up in the elasticsearch level
where we are merging results from shards or results from indexes (maybe
elasticsearch doesn't bother to merge twice but merges once), that's also a
mem space I'd like to collect data on.
I think a per query mem use would also be something interesting, though,
perhaps obviously too much to keep up with for every query (maybe a future
opt-in feature, unless it's already there and I'm missing it).
Other cluster events like nodes entering and exiting the cluster or the
changing of the master would be nice to collect.
I'm guessing some of this isn't available and some of it is, but my
Google-Fu seems to be lacking. I'm pretty sure I can poll to figure out
the events happened, but was wondering if there was something in the java
client node where I could get a Future or some other hook to turn it into a
push instead of a pull.
Any help will be appreciated. I'm aware it's a wide net though.
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/56362f94-c20b-4201-ae15-5f5f9ca77ff4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.