You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2018/07/26 15:30:24 UTC

[GitHub] pdeva opened a new issue #6046: allow 'secondary' deep storage to easily allow deep storage migration

pdeva opened a new issue #6046: allow 'secondary' deep storage to easily allow deep storage migration
URL: https://github.com/apache/incubator-druid/issues/6046
 
 
   currently if you want to migrate your deep storage, it is a very manual procedure, with tons of downtime.
   
   To automate this, Druid needs the ability to specify a 'secondary' deep storage.
   This way, if i want to migrate from say S3 to GCloud, I would:
   
   1. Specify both S3 and GCloud as deep storage.
   2. All segments from here on are stored in *both* deep storages
   3. When fetching, both deep storages are checked for presence of segment
   4. When time interval 'x' has passed, enough segments would have been stored in Gcloud that i would turn off 'S3' deep storage. 
   
   The above would result in deep storage migration gradually and without any downtime.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org