Hi Sharon, Thanks for your ideas. Some latest stats: dbadmin=> select get_ahm_epoch();select get_current_epoch();select get_last_good_epoch();select * from vs_epochs; get_ahm_epoch --------------- 4290523 (1 row) get_current_epoch ------------------- 4290669 (1 row) get_last_good_epoch -------------...

Hi Sharon, Thanks for the feedback. We're witnessing ROS growth across multiple projections. FYI our DB has 1147 tables, supported by 4226 projections and a total of 58550 columns. Table row counts vary, but on average we have 11 million rows per table. I have been inspecting the tuple_mover_operati...

This is a known issue in certain versions of Vertica with the export_objects command. We use export_catalog to get the entire catalog and then grab the view/projection/table definitions from there. The views table is only useful if the view definition is less than 2000 characters, we have very large...

Since upgrading from 5.0.8 to 6.1.0 and 6.1.1 we are seeing constant growth in ROS containers after a period of uptime since a DB or node restart. I confirm this by querying the projection_storage table for ros_count. Initially, ROS container volumes are maintained, but over time, my queries to the ...

Hi sKwa, Thanks, I should have mentioned that we've set the overcommit_memory config parameter to 0 as advised by vertica (we're running RHEL 6). Vertica themselves state: "Vertica process shouldn't use any swap space. If Vertica process starts using swap, there is a configuration issue. If Vertica ...

We're witnessing growth in the swap space used by vertica processes on both a 6.1.0 and 6.1.1 cluster. We allocate just the recommended 2GB to swap, yet over time, vertica begins to consume swap until 2GB is reached. Restarting the vertica process recovers the used swap space. Is anyone else witness...

As part of ongoing maintenance of our 3 node 6.1.0 Vertica database we had to shutdown the database. During this process we attempted to forcefully close all the sessions using the select close_all_sessions(); Unfortunately this did not close all the sessions. One remained and could not be closed di...