Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-5708

Test failure with invalid GetExecSummary; potential coord. race

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • Impala 2.10.0
    • Impala 2.10.0
    • Backend

    Description

      A jenkins test job failed in

      query_test.test_queries.TestHdfsQueries.test_union[exec_option: {'batch_size': 0, 'num_nodes': 0, 'disable_codegen_rows_threshold': 0, 'disable_codegen': True, 'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format: seq/bzip/block] (from pytest)
      

      with the following stack trace in the pytest:

      query_test/test_queries.py:90: in test_union
          result = self.execute_query(query_string, vector.get_value('exec_option'))
      common/impala_test_suite.py:506: in wrapper
          return function(*args, **kwargs)
      common/impala_test_suite.py:531: in execute_query
          return self.__execute_query(self.client, query, query_options)
      common/impala_test_suite.py:598: in __execute_query
          return impalad_client.execute(query, user=user)
      common/impala_connection.py:160: in execute
          return self.__beeswax_client.execute(sql_stmt, user=user)
      beeswax/impala_beeswax.py:194: in execute
          result.exec_summary = self.get_exec_summary(handle)
      beeswax/impala_beeswax.py:213: in get_exec_summary
          self.__build_summary_table(summary, 0, False, 0, False, output)
      beeswax/impala_beeswax.py:252: in __build_summary_table
          for stats in node.exec_stats:
      E   TypeError: 'NoneType' object is not iterable
      

      It looks to me like the returned ExecSummary is wrong or invalid. Nothing very obvious in the logs (attached a snip that I believe is the relevant portion), and I found the profile that was written to the profile log (attached as well). I suspect something may be wrong with the profile because CM doesn't seem to decode it: when I loaded the encoded profile in the CM debug tool "impalaProfileDecoder" (e.g. http://cm-host:7180/cmf/debug/impalaProfileDecoder ), there was no profile details, and exporting as text resulted in a file that just said "Unknown profile.". A next step would be to try to decode the profile in some other way to check validity.

      Attachments

        1. impalad.log
          9 kB
          Matthew Jacobs
        2. profile.b64
          6 kB
          Matthew Jacobs

        Activity

          People

            twmarshall Thomas Tauber-Marshall
            mjacobs Matthew Jacobs
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: