Hi Thibault,
Yes, snapshots are very light to take as it does not copy the hfiles. As
for disk space, per my understanding, it may not be low. Once compaction
happens, snapshot will hold these hfiles which are supposed to be cleaned up.
Hbase master webpage can provide you more information about how much extra
diskspace snapshots takes. Please see the following links for more info. Just
my 2 cents, Experts here may correct/provide more information.
https://issues.apache.org/jira/secure/attachment/12802250/master-snapshot.png
<https://issues.apache.org/jira/secure/attachment/12802250/master-snapshot.png>
https://issues.apache.org/jira/browse/HBASE-15415
<https://issues.apache.org/jira/browse/HBASE-15415>
Thanks,
Huaxiang
> On May 18, 2016, at 3:45 AM, thib <thibault.godo...@gresearch.co.uk> wrote:
>
> Hi,
>
> I am thinking to implement regular snapshots on HBase to protect against
> user mistakes, e.g. if something bad happens go back to the previous
> snapshot.
> I am thinking to keep something as one snapshot per week for four weeks, and
> one snapshot a day for 7 days, so always have about 11 snapshots. Then each
> time a new snapshot is created, an old one would be deleted.
>
> From reading the doc I get the impression that snapshots are quite light to
> take, and have zero on-going performance impact, i.e. HBase will be just as
> fast with 11 snapshots than with none.
> Is that right?
>
> Am I also right to believe that the extra disk usage be very low in our
> setup where we never deleted any data, just add more?
>
> Finally, is anyone aware of a tool / helper script to implement such a
> snapshot strategy, before I spend time writing my own?
>
> Thank you,
> Thibault.
>
>
>
> --
> View this message in context:
> http://apache-hbase.679495.n3.nabble.com/Snapshot-performance-and-helper-script-tp4080073.html
> Sent from the HBase User mailing list archive at Nabble.com.
