Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Not A Problem
-
1.6.0
-
None
-
None
Description
From ACCUMULO-2876, where VolumeManagerImpl.get() was changed to use a site configuration instead of a system, ZooKeeper-based configuration:
Since the Configuration isn't used for anything else inside of VolumeManager, maybe instead of passing in a Configuration, VolumeManagerImpl always uses a SiteConfiguration, can accept a VolumeChooser implementation (falling back to the default for the Property when not provided), and then add Property.GENERAL_VOLUME_CHOOSER to the fixedProperties in Property class to ensure that no one thinks that they can dynamically change it.
The work here is to make the property fixed.
Attachments
Issue Links
- relates to
-
ACCUMULO-2876 Unexpected looping from HdfsZooInstance.getInstanceID()
- Resolved