[IMPALA-6851] custom cluster test TestGrantRevoke::test_role_update doesn't clean up restarted impala daemons correctly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: Impala 2.12.0
• Fix Version/s: Impala 3.0
• Component/s: Infrastructure
• Epic Color: ghx-label-9
• Assignee: Tianyi Wang
• Reporter: Tianyi Wang
• Created: 13/Apr/18 20:37
• Updated: 13/Apr/18 20:44
• Resolved: 13/Apr/18 20:44

Description

In TestGrantRevoke::test_role_update, one of the impala daemons is restarted. When the test finishes, it doesn't kill or wait for the restarted process. There are several problems of not doing so:

• When another custom cluster test attempts to kill the impala daemon, the impala daemon will become a zombie process. The PID won't go away until the py tests process exits. start-impala-cluster.py doesn't handle this case correctly and will time out. Fortunately, test_role_update is always the last test in custom cluster tests, so it doesn't break builds for now.
• It leaks PID and process information in the kernel as long as the py test process is running.

Issue Links

• duplicates: IMPALA-5695 test_role_update test leaves the mini-cluster in a bad state after execution