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 "Joe McDonnell (Jira)" <ji...@apache.org> on 2020/06/17 15:06:00 UTC
[jira] [Resolved] (IMPALA-9435) Usability enhancements for the data
cache access trace
[ https://issues.apache.org/jira/browse/IMPALA-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe McDonnell resolved IMPALA-9435.
-----------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> Usability enhancements for the data cache access trace
> ------------------------------------------------------
>
> Key: IMPALA-9435
> URL: https://issues.apache.org/jira/browse/IMPALA-9435
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 3.4.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Major
> Fix For: Impala 4.0
>
>
> In IMPALA-8542, we added an access trace to the data cache. This outputs a JSON entry with information about each hit/miss. Currently it is controlled by the data_cache_enable_tracing startup parameter, and it will trace all accesses to a single file. There are a few enhancements that would make this easier to enable:
> # Limit the number of access trace entries stored on disk to avoid unlimited disk usage. This can be done by switching to use be/src/util/simple-logger.h rather than a single file. The number of retained entries should be configurable.
> # Implement a way to trace a subset of accesses (e.g. 5%)
> # Optionally provide a way to start/stop logging without restart (e.g. via the WebUI)
--
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