Unable to mergeout data from retired storage location

Jeff_Anderson

We have a 6-node Vertica cluster running 7.0 that I recently added new storage locations to.  After adding the locations, I realized that two of the nodes did not appear to be using the new data storage.  I found that I had given two of my nodes relative paths to the ADD_LOCATION function (i.e. 'myData/Path' instead of '/myData/Path') and Vertica had created a data directory inside the catalog directory on both of those nodes.

I'm trying to retire and mergeout the data in these locations because: 1) The documentation says that having data in the catalog is a bad idea and 2) having data in this location appears to be creating errors for the vbr.py backup script causing it to fail.

I have tried to manually mergeout the data with the DO_TM_TASK function, preformed a purge and then a manual mergeout, and attempted mergeouts on projections individually. A small amount of data (~8GB) remains on the locations and Vertica prevents me from dropping it.

Any help would be greatly appreciated

Raul_1

This task will be simpilified in the 7.1 release with the following function - MOVE_RETIRED_LOCATION_DATA
http://my.vertica.com/docs/7.1.x/HTML/index.htm#Authoring/SQLReferenceManual/Functions/VerticaFunctions/MoveRetiredLocationData.htm?Highlight=move%20storage%20location

Jeff_Anderson

Thanks for the heads up Raul.  Do you know of  a not-as-simple way to force the mergeout in 7.0?

Raul_1

Using do_tm_task is the only way I am aware of in versions prior to 7.1