Vacuum/Reindex in AMP :-

Aruba Employee

When we do a vacuum/reindex on AMP, we do full vacuum.

VACUUM FULL does more extensive processing, including moving of tuples across blocks to try to compact the table to the minimum number of disk blocks. This form is much slower and requires an exclusive lock on each table while it is being processed. VACUUM reclaims storage occupied by deleted tuples and makes it available for re-use. In normal PostgreSQL operation, tuples that are deleted or obsoleted by an update are not physically removed from their table; they remain present until a VACUUM is done.

To vacuum/reindex please run the following commands on AMP CLI :

1. Disable AMP:
# amp_disable

2. Prior to running each db command below (reindex and vacuum) stop and restart the postgres database using the commands:
# service postgresql stop
# service postgresql start
This will remove any queued up nightly jobs and allow the reindex and vacuum jobs to proceed with without waiting in the queue.

2a. If you are a super user for postgres then :
#db
airwave=> reindex database airwave
airwave=> vacuum full analyze

2b. For normal root login users, run the following commands:
AMP Version < 7.3
# /opt/airwave/bin/reindexdb -d airwave -Upostgres
# /opt/airwave/bin/vacuumdb -v -f -z -Upostgres airwave
AMP Version >= 7.3
# /opt/airwave/pgsql/bin/reindexdb -d airwave -Upostgres
# /opt/airwave/pgsql/bin/vacuumdb -v -f -z -Upostgres airwave

2c. or you can also run these for normal root login users :

# psql -Upostgres airwave
psql (8.4.4)
Type "help" for help.

airwave=# reindex database airwave;
REINDEX
airwave=# vacuum full analyze;
VACUUM
airwave=#

3. Enable AMP bye :
# amp_enable

Version history
Revision #:
1 of 1
Last update:
‎06-30-2014 11:22 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.