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 "Kurt Deschler (Jira)" <ji...@apache.org> on 2021/03/31 04:39:00 UTC

[jira] [Resolved] (IMPALA-10504) Add tracing for remote block reads

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

Kurt Deschler resolved IMPALA-10504.
------------------------------------
    Fix Version/s: Impala 4.0
       Resolution: Fixed

> Add tracing for remote block reads
> ----------------------------------
>
>                 Key: IMPALA-10504
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10504
>             Project: IMPALA
>          Issue Type: Improvement
>            Reporter: Kurt Deschler
>            Assignee: Kurt Deschler
>            Priority: Major
>             Fix For: Impala 4.0
>
>
> While chasing performance issues, there were a large number of remote block read messages in the logs. Need tracing to track down the source of these. 
> {noformat}
>     Errors: Read 3.07 GB of data across network that was expected to be local.
> Block locality metadata for table 'tpcds_600_parquet.store_sales' may be stale.
> This only affects query performance and not result correctness.
> One of the common causes for this warning is HDFS rebalancer moving some of the file's blocks.
> If the issue persists, consider running "INVALIDATE METADATA `tpcds_600_parquet`.`store_sales`"{noformat}
>  



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org