The query spends time queuing prior to running You can find additional information in STL_UNDONE. You can view rollbacks by querying STV_EXEC_STATE. If a data manipulation language (DML) operation encounters an error and rolls back, the operation doesn't appear to be stopped because it is already in the process of rolling back. The return to the client from the leader node.The return to the leader node from the compute nodes. Check STV_EXEC_STATE to see if the query has entered one of these return phases: Here are some common reasons why a query might appear to run longer than the WLM timeout period: The query is in the "return" phase Use the STV_EXEC_STATE table for the current state of any queries that are actively running on compute nodes: select * from STV_EXEC_STATE where query = your_query_id ORDER BY segment, step, slice Use this query for more information about query stages: select * from SVL_QUERY_REPORT where query = your_query_id ORDER BY segment, step, slice To view the status of a running query, query STV_INFLIGHT instead of STV_RECENTS: select * from STV_INFLIGHT where query = your_query_id For more information about query planning, see Query planning and execution workflow. However, the query doesn't use compute node resources until it enters STV_INFLIGHT status. When the query is in the Running state in STV_RECENTS, it is live in the system. When querying STV_RECENTS, starttime is the time the query entered the cluster, not the time that the query begins to run. For example, the query might wait to be parsed or rewritten, wait on a lock, wait for a spot in the WLM queue, hit the return stage, or hop to another queue. If WLM doesn’t terminate a query when expected, it’s usually because the query spent time in stages other than the execution stage. A WLM timeout applies to queries only during the query running phase.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |