[
https://issues.apache.org/jira/browse/IMPALA-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-4487.
-----------------------------------
Resolution: Cannot Reproduce
We fixed a lot of issues in the stress test last year.
> stress test occasionally leaves runners lingering
> -------------------------------------------------
>
> Key: IMPALA-4487
> URL: https://issues.apache.org/jira/browse/IMPALA-4487
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 2.8.0
> Reporter: Michael Brown
> Priority: Major
> Labels: stress
> Attachments: stacks.txt
>
>
> The stress test runner {{concurrent_select.py}} sometimes continues to run
> after all the requested queries have been executed. This will be evident from
> the console report: the number of Done queries will be the number of queries
> set by {{concurrent_select.py --max-queries}} but {{concurrent_select.py}}
> will just continue to run indefinitely until terminated.
> I've looked at a cluster at this state and can't evidence of any queries in
> flight or hung. It leads me to believe then that the bug lies in the test
> infrastructure, not Impala.
> The debug logs show this over and over:
> {noformat}
> 08:37:53 2845 140608723109632 DEBUG:concurrent_select[398]:Producer is alive:
> False
> 08:37:53 2845 140608723109632 DEBUG:concurrent_select[399]:Consumer is alive:
> False
> 08:37:53 2845 140608723109632 DEBUG:concurrent_select[400]:Queue size: 0
> 08:37:53 2845 140608723109632 DEBUG:concurrent_select[401]:Runners: 1
> {noformat}
> *Workaround:*
> Send {{SIGTERM}} to the hung child process.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
