Managing local disk write latency in Jira Data Center
Local disk write latency indicator measures the time taken to write data to the local disk on each Jira Data Center node. This metric is crucial for understanding the performance of individual nodes within your Jira Data Center cluster.
Thresholds: | |
---|---|
Optimal | Less than 5ms |
Requires attention | Between 5ms - 15ms |
Needs attention | Greater than 15ms |
How does high local disk write latency affect Jira Data Center performance
High local disk write latency can significantly impact your Jira Data Center instance in several ways:
Slower Lucene search operations (JQL queries)
Increased time for issue creation and updates
Delayed node-to-node cache communications
Extended reindexing times (full, background, and project reindexes)
Overall degradation of Jira performance and user experience
Consistently high Local Disk Write Latency on one or more nodes can lead to performance inconsistencies across your Jira Data Center cluster.
What's the recommendation?
You should aim to keep the local disk write latency below 1ms for optimal performance. If you're consistently seeing latencies above 1ms, consider the following actions:
Check for environmental factors
Verify platform compatibility
Optimize disk configuration
Diagnose runtime issues
Check for environmental factors
Various environmental factors can contribute to high Local Disk Write Latency.
Common environmental factors to investigate:
Anti-virus software: Ensure it's not interfering with Jira's disk operations
Remote or shared drives: Verify that local home directories are on local disks
Virtualized environments: Check for any VM-specific disk performance issues
Ongoing maintenance tasks: Look for disk defragmentation or backup processes
File system encryption or compression: Assess their impact on write performance
Steps to mitigate environmental factors:
Configure anti-virus software to exclude Jira directories from real-time scanning
Ensure local home directories are on high-performance local storage
Optimize VM settings for disk I/O performance
Schedule maintenance tasks during off-peak hours
Evaluate the necessity of file system encryption or compression
See our guide on Interpreting infrastructure metrics for in-product diagnostics.
Verify platform compatibility
Ensuring your local disk setup is compatible with Jira Data Center requirements is essential for optimal performance.
Key compatibility checks:
Verify that you're using supported operating systems and file systems
Ensure local home directories are not on NFS mounts (not supported for Jira DC)
Check that your storage solution meets Jira's I/O performance requirements
Refer to the Supported platforms for Jira Data Center documentation
If you identify compatibility issues:
Plan to migrate to supported platforms if necessary
Consider upgrading storage hardware to meet performance requirements
Consult with your infrastructure team to ensure optimal configuration
Optimize disk configuration
Proper disk configuration is critical for maintaining low Local Disk Write Latency in Jira Data Center.
Optimization steps:
Ensure local home directories are on SSDs or high-performance HDDs
Optimize file system settings for write performance
Consider separating Jira's local home directory from the OS and application directories
Refer to the Installing Jira Data Center guide for more details
Diagnose runtime issues
Java Flight Recorder (JFR) can provide valuable insights into JVM behavior that might be contributing to local disk latency.
Using Java Flight Recorder:
Enable JFR on all Jira Data Center nodes
Collect JFR recordings during periods of high Local Disk Write Latency
Analyze the recordings to identify any JVM-related issues affecting disk performance
See our guide on Diagnosing runtime issues using the Java Flight Recorder
Interpreting JFR results:
Identify any threads that are blocking I/O operations
Check for patterns in disk access that might indicate inefficient data access or caching
Additional considerations for Jira Data Center:
Monitor local disk write Latency across all nodes to identify any inconsistencies
Ensure that all nodes have similar hardware specifications and configurations
Consider the impact of cluster-wide operations (e.g., reindexing) on local disk performance
Regularly review and optimize Jira's database and index configurations to reduce disk I/O