commit | 155ffd64ee3562c36d5000de3a5102e05b393cc2 | [log] [tgz] |
---|---|---|
author | Sahil Takiar <takiar.sahil@gmail.com> | Thu Sep 03 15:50:43 2020 -0700 |
committer | Sahil Takiar <stakiar@cloudera.com> | Tue Sep 22 23:45:57 2020 +0000 |
tree | 5a5007957f5926476d84db9abc4b91e08e5ffbc5 | |
parent | dcdbaf12224e7029dde3110d56edea022dd3a2a0 [diff] |
IMPALA-9046: Profile counter that indicates if a JVM pause occurred Adds a new section to the host profiles that includes JVM GC related metrics. These metrics are taken from JMX and the JvmPauseMonitor. The host profiles will now include a section like below: JVM: - GcCount: 19 - GcNumInfoThresholdExceeded: 0 - GcNumWarnThresholdExceeded: 0 - GcTimeMillis: 17s476ms - GcTotalExtraSleepTimeMillis: 380 GcNumInfoThresholdExceeded, GcNumWarnThresholdExceeded, and GcTotalExtraSleepTimeMillis are all taken from JvmPauseMonitor. GcCount and GcTimeMillis are taken from JMX (specifically, GarbageCollectorMXBean). The counters themselves are derived from the impalad host-level metrics. Changed the 'lock_' in JvmMetricCache (in memory-metrics.h) from a mutex to a shared_mutex. Most accessors of the JvmMetricCache member variables are read-only. A write only occurs lazily at most every second. This should help reduce lock contention on JvmMetricCache now that all queries will start accessing info stored by the JvmMetricCache. Testing: * Ran core tests * Added a test that runs Java UDF, which triggers JVM GC Change-Id: Idbaae2f9142b8be94532a0a147668a3d96091b0b Reviewed-on: http://gerrit.cloudera.org:8080/16414 Reviewed-by: Tim Armstrong <tarmstrong@cloudera.com> Reviewed-by: Sahil Takiar <stakiar@cloudera.com> Tested-by: Sahil Takiar <stakiar@cloudera.com>
Lightning-fast, distributed SQL queries for petabytes of data stored in Apache Hadoop clusters.
Impala is a modern, massively-distributed, massively-parallel, C++ query engine that lets you analyze, transform and combine data from a variety of data sources:
To learn more about Impala as a business user, or to try Impala live or in a VM, please visit the Impala homepage. Detailed documentation for administrators and users is available at Apache Impala documentation.
If you are interested in contributing to Impala as a developer, or learning more about Impala's internals and architecture, visit the Impala wiki.
Impala only supports Linux at the moment. Impala supports x86_64 and has experimental support for arm64 (as of Impala 4.0). Impala Requirements contains more detailed information on the minimum CPU requirements.
This distribution uses cryptographic software and may be subject to export controls. Please refer to EXPORT_CONTROL.md for more information.
See Impala's developer documentation to get started.
Detailed build notes has some detailed information on the project layout and build.