[GitHub] [fluo-muchos] karthick-rn opened a new pull request #352: Update init scope when using multiple volumes in Accumulo 2.1

[GitBox <gi...@apache.org>]

karthick-rn opened a new pull request #352:
URL: https://github.com/apache/fluo-muchos/pull/352


   When multiple volumes are used, Accumulo can randomly place metadata tables and WALs on any of the volumes during the init step. When using Muchos with Accumulo 2.0, we have overcome this by running the init first with `HDFS` as `instance.volumes` and after that add the other volumes like ABFS,S3, etc.. This 2 step approach is no longer needed in Accumulo 2.1, this PR adds the new property `general.custom.volume.preferred.init` to Muchos which will direct 
   all the metadata tables and WALs to the volume specified in this property. I have tested this change with 2.1.0-SNAPSHOT & also ensured the existing code still works with 2.0.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [fluo-muchos] karthick-rn merged pull request #352: Update init scope when using multiple volumes in Accumulo 2.1

[GitBox <gi...@apache.org>]

karthick-rn merged pull request #352:
URL: https://github.com/apache/fluo-muchos/pull/352


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org