# How expensive is querying the cluster health **URL:** \ **Category:** Elasticsearch\ **Created:** [January 20, 2018, 1:58pm UTC](https://discuss.elastic.co/t/how-expensive-is-querying-the-cluster-health/116340 "2018-01-20T13:58:26Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![JeroenSoeters](https://avatars.discourse-cdn.com/v4/letter/j/8edcca/32.png) [@JeroenSoeters](https://discuss.elastic.co/u/JeroenSoeters)\ **Post date:** [January 20, 2018, 1:58pm UTC](https://discuss.elastic.co/t/how-expensive-is-querying-the-cluster-health/116340/1 "2018-01-20T13:58:26Z")
I would like to understand better how expensive the client.admin().cluster().prepareHealth().get().getStatus() is. Is this something you can do every 10 seconds, every second, multiple times per second? What is the impact? I'm using ES 2.4 right now. ---
**Author:** ![s1monw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s1monw/32/3637_2.png) [@s1monw](https://discuss.elastic.co/u/s1monw)\ **Post date:** [January 26, 2018, 12:54pm UTC](https://discuss.elastic.co/t/how-expensive-is-querying-the-cluster-health/116340/2 "2018-01-26T12:54:34Z")
do you want to get the status of the cluster then just use the default endpoint `/` it will be fast and will give you a 200 unless the cluster is red then it will respond with a `500`. you can also hammer it with requests that should be fine. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 23, 2018, 12:54pm UTC](https://discuss.elastic.co/t/how-expensive-is-querying-the-cluster-health/116340/3 "2018-02-23T12:54:41Z")
Closed on February 23, 2018, 12:54pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.