[IMPALA-4438] test_failpoints.py fails on ec2 c3 machines; works on m2 machines

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: Impala 2.8.0
• Component/s: Infrastructure
• Labels: asf
• Environment: Ubuntu 14.04 ec2 c3.4xlarge vs. ec2 m2.2xlarge
• Assignee: Jim Apple
• Reporter: Jim Apple
• Created: 07/Nov/16 05:01
• Updated: 09/Nov/16 17:57
• Resolved: 09/Nov/16 17:57

Description

This test fails on one AWS instance type and works on another:

_________________ ERROR collecting failure/test_failpoints.py __________________
failure/test_failpoints.py:89: in add_test_dimensions
    node_id_map = TestFailpoints.parse_plan_nodes_from_explain_output(QUERY, "functional")
failure/test_failpoints.py:73: in parse_plan_nodes_from_explain_output
    explain_result = client.execute("explain " + QUERY)
common/impala_connection.py:160: in execute
    return self.__beeswax_client.execute(sql_stmt, user=user)
beeswax/impala_beeswax.py:195: in execute
    result.log = self.get_log(handle.log_context)
beeswax/impala_beeswax.py:371: in get_log
    return self.__do_rpc(lambda: self.imp_service.get_log(query_handle))
beeswax/impala_beeswax.py:454: in __do_rpc
    raise ImpalaBeeswaxException("Not connected", None)
E   ImpalaBeeswaxException: ImpalaBeeswaxException:
E    Not connected

Issue Links

• blocks: IMPALA-3229 Allow all contributors (or at least committers?) to run GVM