[IMPALA-4689] Expiration computes last active timestamp wrong

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Impala 2.7.0
• Fix Version/s: Impala 2.9.0
• Component/s: Backend
• Assignee: Lars Volker
• Reporter: Lars Volker
• Created: 17/Dec/16 01:40
• Updated: 11/Jan/17 15:02
• Resolved: 04/Jan/17 12:25

Description

The last active time in impala-server.cc#L1806 is in milliseconds, but the TimestampValue c'tor expects seconds.

          VLOG_QUERY << "Expiring query due to client inactivity: "
                     << expiration_event->second << ", last activity was at: "
                     << TimestampValue(query_state->last_active()).DebugString();
          const string& err_msg = Substitute(
              "Query $0 expired due to client inactivity (timeout is $1)",
              PrintId(expiration_event->second),
              PrettyPrinter::Print(timeout_s * 1000000000L, TUnit::TIME_NS));