I think it would be a good idea to have the PreferredVolumeChooser select volumes during init. Looks like there is already an issue open for this: https://github.com/apache/accumulo/issues/1373
I imagine you could move a table to a different volume by changing the preferred volume configuration and then compacting the table. But as Keith mentions in the issue, it would be easier if this weren't necessary. Billie On Tue, Nov 19, 2019, 3:45 PM karthick rn <karthick.narend...@gmail.com> wrote: > Hi, > > When provisioning multiple volumes, for ex. HDFS & Azure Data Lake storage, > it would be good to choose which volume we want the system tables like > metadata, root, replication tables to be created. Currently, Accumulo > randomly creates these tables on multiple volumes and the only way to > control this is to run Accumulo init on 1st volume so all system tables get > created on this volume and then add the other volumes. > > I have also tried running 'config -t accumulo.metadata -s > table.custom.volume.preferred=hdfs://accucluster/accumulo' in an attempt to > move the metadata table to a preferred volume, in this case HDFS, but I > don’t see metadata table under HDFS. Also, ‘config -f > table.custom.volume.preferred’ does not show anything! > In short, I was wondering if there is any provision to "move" these system > tables across volumes, or is that a non-goal by design? > > Many thanks > > Regards, > Karthick >
