When loading a large dataset and creating the index, the Database Specialist encounters the following error message from Aurora:ERROR: cloud not write block 7507718 of temporary file: No space left on deviceWhat is the cause of this error and what should the Database Specialist do to resolve this issue?
The scaling of Aurora storage cannot catch up with the data loading. The Database Specialist needs to modify the workload to load the data slowly.
The scaling of Aurora storage cannot catch up with the data loading. The Database Specialist needs to enable Aurora storage scaling.
The local storage used to store temporary tables is full. The Database Specialist needs to scale up the instance.
The local storage used to store temporary tables is full. The Database Specialist needs to enable local storage scaling.
Explanations:
The error is related to local storage and not the pace of data loading. Slowing down the data load won’t resolve the issue of temporary storage filling up.
Aurora storage scaling is designed to automatically adjust storage capacity for persistent storage, but the issue here involves local temporary storage used for operations like creating indexes, not Aurora’s overall storage.
The error occurs when the local storage, which is used to store temporary tables and intermediate data, is full. Scaling up the instance can increase the available local storage for these temporary operations.
Aurora automatically manages local storage scaling for temporary files. There is no manual option to enable local storage scaling as Aurora handles this behind the scenes for instance types. Scaling up the instance is the correct solution.