You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Michael Ho (JIRA)" <ji...@apache.org> on 2018/07/15 23:41:00 UTC
[jira] [Updated] (IMPALA-6766) Resource management for network
[ https://issues.apache.org/jira/browse/IMPALA-6766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Ho updated IMPALA-6766:
-------------------------------
Parent Issue: IMPALA-7301 (was: IMPALA-5865)
> Resource management for network
> -------------------------------
>
> Key: IMPALA-6766
> URL: https://issues.apache.org/jira/browse/IMPALA-6766
> Project: IMPALA
> Issue Type: Sub-task
> Components: Distributed Exec
> Affects Versions: Impala 3.0, Impala 2.12.0
> Reporter: Michael Ho
> Priority: Major
> Labels: resource-management, scalability
>
> There is no way to manage the network bandwidth usages of a query. In other words, a query which shuffles a huge amount of data can slow down other concurrent queries. The followings are the observed bandwidth of a query when it's run alone and when it's run with another query which shuffles a lot of data across the network. We should consider extending the resource pool concept to also manage network usage.
>
> {noformat}
> Good case:
> DataStreamSender (dst_id=4)
> - BytesSent: 828.3 MiB (868564531)
> - InactiveTotalTime: 0ns (0)
> - NetworkThroughput(*): 706.4 MiB/s (740751383)
>
> Bad case:
> DataStreamSender (dst_id=4)
> - BytesSent: 828.3 MiB (868564531)
> - InactiveTotalTime: 0ns (0)
> - NetworkThroughput(*): 182.3 MiB/s (191106930)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org