800GB/20TB = 4%.
You've got a 20TB database, and run out of space when
4% is added.
Either you're running way to close to the edge, or I misunderstand something.
Either way, enable auto-scaling.
https://aws.amazon.com/about-aws/whats-new/2019/06/rds-storage-auto-scaling/On 8/9/22 10:29, Taylor Smith wrote:
Yes, the database was always going to be a minimum of 20TB however we build the indexes on the partition which at max is about 1.3TB, which in temp files will use about 800GB temporary files. Note it doesn't have the same effect when doing non-concurrently. I don't think rolling off would help as its likely largest partition will either be the current month or the previous month so the problem would still persist.
> On Aug 9, 2022, at 7:45 AM, Taylor Smith <taylorjrsmith@gmail.com> wrote:
>
> Thanks Rob,
>
> This is what I was thinking. Would you say it presents any risk then having a database unable to rebuild its own indexes if needed?
>
>
No I would not. The scale-up + rebuild should tell you how much you actually need and if you’ve over done the scale up you can scale down to what you need. Was the original spec expecting 20+T? Any chance of rolling older months off to some other node?
--
Angular momentum makes the world go 'round.