[ https://issues.apache.org/jira/browse/ACCUMULO-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995086#comment-13995086 ]
Keith Turner commented on ACCUMULO-2793: ---------------------------------------- bq. So I can just never list the defunct volume in the instance.volumes property? Yeah, should remove it from {{instance.volumes}} when setting the replacement. I checked w/ {{VolumeIT}} to ensure this scenario was tested, and it is. Leaving it would probably cause new files to be placed in the defunct volume. I took a look at {{ServerConstants.getVolumeReplacements()}} It does require that the new volume is present like you mentioned. > Clean up handling of moving HDFS under Accumulo from non-HA to HA > ----------------------------------------------------------------- > > Key: ACCUMULO-2793 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2793 > Project: Accumulo > Issue Type: Bug > Components: docs > Affects Versions: 1.6.0 > Reporter: Sean Busbey > Priority: Blocker > Fix For: 1.6.1, 1.7.0 > > > We added a util to handle cluster maintenance (such as going from non-HA HDFS > to HA HDFS) in ACCUMULO-1832. > It should be added to section 13.5 Tools in the user manual, and a reference > to that section should be added in the section 12 explanation of the impact > of supporting multi-volume setups. -- This message was sent by Atlassian JIRA (v6.2#6252)