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 Smith (Jira)" <ji...@apache.org> on 2023/01/30 21:33:00 UTC
[jira] [Created] (IMPALA-11883) erasure-coded-bytes-read metric doesn't work for Ozone
Michael Smith created IMPALA-11883:
--------------------------------------
Summary: erasure-coded-bytes-read metric doesn't work for Ozone
Key: IMPALA-11883
URL: https://issues.apache.org/jira/browse/IMPALA-11883
Project: IMPALA
Issue Type: Bug
Components: Backend
Affects Versions: Impala 4.3.0
Reporter: Michael Smith
The {{erasure-coded-bytes-read}} metric only works for HDFS because it relies on the HDFS-specific function {{hdfsFileGetReadStatistics}}. We have other ways to track bytes read: by looking at the actual read operations. {{hdfsFileGetReadStatistics}} is only needed for tracking things we don't have visibility into such as locality and short-circuit reads.
Update {{erasure-coded-bytes-read}} to gather metrics from actual reads similar to what we do for {{bytes-read}}. Note that the semantics are different: {{bytes-read}} includes reads from memory, local buffer, and cached files; we should omit those as they're not erasure-coded reads.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org