# CrateDB database logs showing "shard is now inactive", and threads are getting blocked

**URL:** <https://community.cratedb.com/t/cratedb-database-logs-showing-shard-is-now-inactive-and-threads-are-getting-blocked/1617>\
**Category:** CrateDB\
**Created:** [October 5, 2023, 7:59am UTC](https://community.cratedb.com/t/cratedb-database-logs-showing-shard-is-now-inactive-and-threads-are-getting-blocked/1617 "2023-10-05T07:59:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![hammerhead](https://sea2.discourse-cdn.com/flex020/user_avatar/community.cratedb.com/hammerhead/32/270_2.png) [@hammerhead](https://community.cratedb.com/u/hammerhead)\
**Post date:** [October 5, 2023, 12:43pm UTC](https://community.cratedb.com/t/cratedb-database-logs-showing-shard-is-now-inactive-and-threads-are-getting-blocked/1617/2 "2023-10-05T12:43:46Z")

</div>

Hi @Satishlk,

the “shard is now inactive” message is printed when there haven’t been any newly written records for specific shards for a certain time. The message itself is not problematic and can occur during regular operations:

> <https://github.com/crate/crate/blob/fd4567977cf2d8be22902e2b7679b2d51c1f9181/server/src/main/java/org/elasticsearch/index/shard/IndexShard.java#L1705>

Whenever there are any performance issues, it is advisable to check metrics accessible through the Crate JMX Exporter as described below:

> [@Monitoring an on-premises CrateDB cluster with Prometheus and Grafana](https://community.cratedb.com/t/monitoring-an-on-premises-cratedb-cluster-with-prometheus-and-grafana/1236):
>
> If you are running CrateDB in a production environment, you have probably wondered what would be the best way to monitor the servers to identify issues before they become problematic and to collect statistics that you can use for capacity planning. We recommend pairing two well-known OSS solutions, [Prometheus](https://prometheus.io/) which is a system that collects and stores performance metrics, and [Grafana](https://grafana.com/) which is a system to create dashboards. For a CrateDB environment, we are interested in: CrateDB-specific m…

From our experience, 64 GB RAM sounds relatively low in relation to the 32 vCPU cores. The JMX Exporter gives access to metrics that help identify bottlenecks. For example, GC rates and heap usage (circuit breaker utilization) can indicate if the cluster is running low on the available heap.

Therefore, if you haven’t done so already, I recommend getting the JMX Exporter set up to gain access to application-level performance metrics.

---

_[View the full topic](https://community.cratedb.com/t/cratedb-database-logs-showing-shard-is-now-inactive-and-threads-are-getting-blocked/1617)._