[IMPALA-5397] Set "End Time" earlier rather than on unregistration.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 2.9.0
• Fix Version/s: Impala 3.2.0
• Component/s: Backend
• Labels: admission-control query-lifecycle
• Target Version: Impala 3.2.0
• Epic Color: ghx-label-8
• Assignee: Pooja Nilangekar
• Reporter: Mostafa Mokhtar
• Created: 31/May/17 16:48
• Updated: 22/Mar/23 08:07
• Resolved: 01/Mar/19 17:50

Description

When queries are executed from Hue and hit the idle query timeout then the query duration keeps going up even though the query was cancelled and it is not actually doing any more work. The end time is only set when the query is actually unregistered.

Queries below finished in 1s640ms while the reported time is much longer.

User	Default Db	Statement	Query Type	Start Time	Waiting Time	Duration	Scan Progress	State	Last Event	rows fetched	Resource Pool	Details	Action
hue/[e-mail]	tpcds_1000_parquet	select count from tpcds_1000_parquet.inventory	QUERY	2017-05-31 09:38:20.472804000	4m27s	4m32s	261 / 261 ( 100%)	FINISHED	First row fetched	1	root.default	Details	Close
hue/[e-mail]	tpcds_1000_parquet	select count from tpcds_1000_parquet.inventory	QUERY	2017-05-31 08:38:52.780237000	2017-05-31 09:38:20.289582000	59m27s	261 / 261 ( 100%)	FINISHED	1	root.default	Details

Issue Links

• causes: IMPALA-12008 End Time in profile is set before DML finishes
• is duplicated by: IMPALA-5555 Add timeline event to query profile to indicate that it is finished
• is related to: IMPALA-5285 Account for missing significant contributors to query time in exec summary
• relates to: IMPALA-5555 Add timeline event to query profile to indicate that it is finished