amazon web services - Disk usage when redshift doing vacuum merge? -

I know that in two steps redshift split vacuum progress: sort and merge.

During the sorting, disk usage will not change, but the merge phase will occupy a lot of free space.

My cluster is 3 nodes of dw2.xlarge, total 480 GB SSD, before vacuuming, the usage of the total disk is approximately 50%.

I am doing a vacuum on a table of 81 GB, but failed to merge due to disk full error.

I want to know how much space should be reserved to clear a large unauthorized table?

I asked this question to redshift a strong team but I have not got any answers yet. Does anyone have experience with it?

Yes for more vacuum use

Refrain from.

When you join it (select ... to ... ...) here you select the sorted order to select so that you put data in the sorted fashion. .

Add incremental according to your sort key (choose * from *) For example if you are collecting data for 30 days then make a deep copy of the day per day. It should avoid issues of space.