[
https://issues.apache.org/jira/browse/IMPALA-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-7643.
-----------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.1.0
|
|!https://mail.google.com/mail/u/0/images/cleardot.gif|id=:2ba!|
|
IMPALA-7643: report # queries actually executing in stress test
With admission control it's interesting to separate out two categories
of queries:
1. Queries that have started up and are executing
2. Queries that have not made it that far yet, e.g. are waiting to
establish a client connection (hitting --fe_service_threads limit),
are in the planner, are queued in admission control or are starting
up.
We now call 1+2 "Active" and 1 "Executing".
Example output:
Done | Active | Executing | Mem Lmt Ex | AC Reject | AC Timeout | Time Out |
Cancel | Err | Incorrect | Next Qry Mem Lmt | Tot Qry Mem Lmt | Tracked Mem |
RSS Mem
0 | 0 | 0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 | |
0 | 10 | 3 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 510 | 3922 | 158 |
4541
0 | 20 | 10 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 390 | 8534 | 570 |
4517
Refactored QueryRunner.run_query() to reduce nesting and make it more
readable.
Testing:
Ran local stress tests with and without --test_admission_control set.
Change-Id: I5692e8e5ba3224becefc24437197bf5a5b450335
Reviewed-on: [http://gerrit.cloudera.org:8080/11587]
Reviewed-by: Impala Public Jenkins
<[[email protected]|mailto:[email protected]]>
Tested-by: Impala Public Jenkins
<[[email protected]|mailto:[email protected]]>
> Report the number of currently queued queries in stress test
> ------------------------------------------------------------
>
> Key: IMPALA-7643
> URL: https://issues.apache.org/jira/browse/IMPALA-7643
> Project: IMPALA
> Issue Type: Sub-task
> Components: Infrastructure
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Fix For: Impala 3.1.0
>
>
> The stress test output when running wiht admission control is confusing
> because it reports queued queries as running, so it looks like we're running
> with many queued queries, but rather they're piled up in admission control.
> We should distinguish somehow.
> {noformat}
> Done | Running | Mem Lmt Ex | AC Reject | AC Timeout | Time Out | Cancel |
> Err | Incorrect | Next Qry Mem Lmt | Tot Qry Mem Lmt | Tracked Mem | RSS Mem
> 230 | 518 | 0 | 0 | 124 | 0 | 12 |
> 0 | 0 | 25 | 11182 | 3061 | 3984
> 243 | 528 | 0 | 0 | 135 | 0 | 12 |
> 0 | 0 | 26 | 11363 | 4065 | 4964
> 255 | 540 | 0 | 0 | 144 | 0 | 12 |
> 0 | 0 | 17 | 11644 | 2744 | 5199
> 261 | 550 | 0 | 0 | 148 | 0 | 12 |
> 0 | 0 | 25 | 11866 | 5038 | 5228
> 266 | 562 | 0 | 0 | 152 | 0 | 12 |
> 0 | 0 | 15 | 12085 | 4515 | 4127
> 271 | 573 | 0 | 0 | 153 | 0 | 12 |
> 0 | 0 | 26 | 12318 | 3676 | 4059
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
