GemFire: Region-owned disk stores are not supported with segmented disk stores. (java.lang.UnsupportedOperationException)
Article ID: 412053
Updated On:
Products
Issue/Introduction
After upgrading the GemFire version from 10.0.x to 10.1.x, GemFire cluster cannot start with the following exception
ERROR Gemfire shutting down! on Init():Region owned disk stores are not supported with segmented disk stores.(java.lang.UnsupportedOperationException)
Environment
GemFire version 10.1.x
Cause
Starting with GemFire 10.1, a new segmented disk store feature is enabled by default for all new disk stores. This feature divides disk stores into segments (subsidiary sub-stores) to improve read/write performance and recovery times—potentially up to 10x faster, depending on your storage setup.
However, the segmented format is incompatible with the legacy "region-owned" disk store model. When your upgraded 10.1.4 instance attempts to load existing disk store files (created under 10.0.4), it detects the legacy format and throws the UnsupportedOperationException because it cannot reconcile region-owned stores with the expected segmented structure.
Resolution
To resolve the issue: Upgrade Disk Stores to Segmented Format
GemFire version 10.1 includes a new disk store implementation, the segmented disk store. The segmented disk store improves the disk store's read and write performance and recovery speed. Beginning with GemFire version 10.1, all new disk stores are created as segmented, while existing disk stores continue to operate as non-segmented. To realize the performance enhancements, all disk stores should be upgraded to segmented disk stores.
Use GemFire's gfsh tool to convert your offline disk store files from the legacy format to segmented. This is a one-time offline operation and is explicitly supported for upgrades to 10.1+, as described in Segmented Disk Store
If upgrading is temporarily not feasible, disable segmented disk stores as described in Disabling Segmented Disk Stores (not recommended for optimal performance). However, this should only be a short-term workaround.
Additional Information
Feedback
