Project

General

Profile

« Previous | Next » 

Revision 13023

Added by Aaron Marcuse-Kubitza over 10 years ago

/README.TXT: Full database import: disk space: documented that a higher high-water mark actually occurs later in the import, so that the disk usage issue actually remains a problem after the very beginning

View differences:

README.TXT
70 70 
			occurs, the problem will often be fixed just by rerunning the import
71 71 
			again. (the high-water mark varies by import.)
72 72 
		although the import schema itself is only 315 GB, Postgres uses
73 
			significant temporary space at the beginning of the import. the
74 
			total disk usage reaches 1.7+ TB in the first hour
75 
			("14:00:25"-"12:55:09"), and then oscillates between 1.2-1.6 TB in
76 
			the following 2+ hours.
73 
			significant temporary space at the beginning of the import.
74 
			the total disk usage oscillates between 1.2-1.8 TB in the first
75 
			3+ hours (for import started @12:55:09, high-water marks of
76 
			1.7 TB @14:00:25, 1.8 TB @15:38:32).
77 77 
		To free up space, remove backups that have been archived on jupiter:
78 78 
			List backups/ to view older backups
79 79 
			Check their MD5 sums using the steps under On jupiter below

Also available in: Unified diff