Copy running for long time
I found a Copy was running for long hours in Dev. When i looked at load_streams, it showed 21% progress, but doesn't move further. It's a simple copy table from local '/home/file1' with delimiter as '~' rejected data '/home/reject1';
Query ran for almost 2 hours and failed due to runtimecap set.
query_requests - memory_acquired_mb showed null, though is_executing is true (i felt this is strange?)
locks - "I" lock was placed on the table but was immediately acquired
execution_engine_profiles - it shows stats around memory acquired, send and receive between nodes, etc. Not sure what else to look for in this table. I specially pulled counters such as memory and execution, but cannot make out how to interpret those.
query_events - did not showed me any pushback from WOS as query did not had any direct hint
I was stuck at a point, trying to understand - how to determine if the transaction was truly running, and if running, what is it actually doing or is it waiting on something?
Table that is being loaded has around 35 cols, max length col is 100 bytes varchar, just one projection which is lazy with literally all the cols in the order by clause and segmented on around first 13 cols. It already has 3.6M records.
searched thru vertica log, did not see any alarming though. So the question is, how to determine if a transaction is truly running or is it hung? if it is running, where it is spending most of the time or waiting on?
Thanks much for any inputs