[IMPALA-6566] TestAdmissionController::test_require_user error - impalad doesn't start because of Java debugger port conflict

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: Not Applicable
• Component/s: Infrastructure
• Labels: flaky
• Epic Color: ghx-label-8
• Assignee: Unassigned
• Reporter: Tim Armstrong
• Created: 23/Feb/18 00:00
• Updated: 02/Mar/18 20:52
• Resolved: 02/Mar/18 20:52

Description

15:51:56 ERROR custom_cluster/test_admission_controller.py::TestAdmissionController::()::test_require_user
15:51:56 ==================================== ERRORS ====================================
15:51:56 _________ ERROR at setup of TestAdmissionController.test_require_user __________
15:51:56 common/custom_cluster_test_suite.py:109: in setup_method
15:51:56     self._start_impala_cluster(cluster_args)
15:51:56 common/custom_cluster_test_suite.py:144: in _start_impala_cluster
15:51:56     check_call(cmd + options, close_fds=True)
15:51:56 /usr/lib64/python2.6/subprocess.py:505: in check_call
15:51:56     raise CalledProcessError(retcode, cmd)
15:51:56 E   CalledProcessError: Command '['/data/jenkins/workspace/impala-asf-2.x-core-asan/repos/Impala/bin/start-impala-cluster.py', '--cluster_size=3', '--num_coordinators=3', '--log_dir=/data/jenkins/workspace/impala-asf-2.x-core-asan/repos/Impala/logs/custom_cluster_tests', '--log_level=1', '--impalad_args="-vmodule admission-controller=3 -fair_scheduler_allocation_path /data/jenkins/workspace/impala-asf-2.x-core-asan/repos/Impala/fe/src/test/resources/fair-scheduler-test2.xml -llama_site_path /data/jenkins/workspace/impala-asf-2.x-core-asan/repos/Impala/fe/src/test/resources/llama-site-test2.xml -disable_admission_control=false -require_username" ', '--state_store_args="-statestore_heartbeat_frequency_ms=100 -statestore_priority_update_frequency_ms=100" ']' returned non-zero exit status 1
15:51:56 ---------------------------- Captured stdout setup -----------------------------
15:51:56 Starting State Store logging to /data/jenkins/workspace/impala-asf-2.x-core-asan/repos/Impala/logs/custom_cluster_tests/statestored.INFO
15:51:56 Starting Catalog Service logging to /data/jenkins/workspace/impala-asf-2.x-core-asan/repos/Impala/logs/custom_cluster_tests/catalogd.INFO
15:51:56 Starting Impala Daemon logging to /data/jenkins/workspace/impala-asf-2.x-core-asan/repos/Impala/logs/custom_cluster_tests/impalad.INFO
15:51:56 Starting Impala Daemon logging to /data/jenkins/workspace/impala-asf-2.x-core-asan/repos/Impala/logs/custom_cluster_tests/impalad_node1.INFO
15:51:56 Starting Impala Daemon logging to /data/jenkins/workspace/impala-asf-2.x-core-asan/repos/Impala/logs/custom_cluster_tests/impalad_node2.INFO
15:51:56 Error starting cluster: Expected 3 impalad(s), only 2 found
15:51:56 
15:51:56 ---------------------------- Captured stderr setup -----------------------------
15:51:56 MainThread: Found 2 impalad/1 statestored/1 catalogd process(es)
15:51:56 MainThread: Found 2 impalad/1 statestored/1 catalogd process(es)
15:51:56 ========= 76 passed, 38 skipped, 1 xfailed, 1 error in 5542.39 seconds =========

Issue Links

• is duplicated by: IMPALA-6369 impalad failed to start due to JDWP error