You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/12/23 18:09:00 UTC

[jira] [Resolved] (IMPALA-7136) Set a default THREAD_RESERVATION_AGGREGATE_LIMIT value

     [ https://issues.apache.org/jira/browse/IMPALA-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong resolved IMPALA-7136.
-----------------------------------
    Resolution: Won't Do

Not sure that this really makes sense with multithreading and other scalability improvements we've made.

> Set a default THREAD_RESERVATION_AGGREGATE_LIMIT value
> ------------------------------------------------------
>
>                 Key: IMPALA-7136
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7136
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Distributed Exec
>            Reporter: Tim Armstrong
>            Priority: Major
>              Labels: resource-management, scalability
>
> Similar to IMPALA-7115, we should consider setting a default value for this option that will reject queries that are likely to be problematic because of scalability concerns. The aggregate thread count really depends on scalability, so [~kwho] probably has the best idea of what a realistic limit is here after the KRPC changes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)