[IMPALA-7478] Add timer to impalad-side of DDLs

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Impala 3.0
• Component/s: Backend
• Epic Color: ghx-label-2
• Assignee: Unassigned
• Reporter: Balazs Jeszenszky
• Created: 23/Aug/18 11:35
• Updated: 23/Aug/18 11:36

Description

Currently, profiles include CatalogOpExecTimer, but aren't helpful if the time is spent on the impalad side. A scoped timer to ProcessCatalogUpdateResult would be useful for clarity.

This is what we've come across:

Query Timeline: 6s001ms
       - Query submitted: 159.835us (159.835us)
       - Planning finished: 1.686ms (1.526ms)
       - Rows available: 5s999ms (5s997ms)
       - First row fetched: 6s000ms (1.027ms)
       - Unregister query: 6s000ms (709.442us)
  ImpalaServer:
     - CatalogOpExecTimer: 3s188ms
     - ClientFetchWaitTimer: 1.690ms
     - RowMaterializationTimer: 0.000ns

Issue Links

• relates to: IMPALA-4830 Add metrics for alter table recover partition