HBASE-29729 Add per-region table descriptor hash to regionServer JMX Metrics #7481
+354
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When table descriptors are modified (e.g., changing compression settings, TTL, or column family configurations), region servers need to reopen regions to pick up these changes. However, there's currently no reliable way to detect which regions are running with stale table descriptors versus the current configuration. This makes it difficult to verify that descriptor changes have propagated correctly across all regions, increasing the risk of configuration drift and making deployment automation more challenging.
This PR adds a tableDescriptorHash field to the per-region JMX metrics exposed by region servers. The hash is a SHA-256 digest of the serialized
TableDescriptorprotobuf, computed once when the region is opened and exposed through theMetricsRegionWrapperinterface. Regions opened with identical table descriptors will produce identical hashes, while any configuration change (compression, TTL, block size, etc.) will produce a different hash. This enables monitoring systems and deployment automation to quickly identify regions that need reopening after table descriptor changes, without parsing and comparing complex nested configuration objects.