[jira] [Updated] (IMPALA-11915) Support timeline and graphical plan exports in the webUI
[ https://issues.apache.org/jira/browse/IMPALA-11915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quanlong Huang updated IMPALA-11915: Fix Version/s: Impala 4.3.0 > Support timeline and graphical plan exports in the webUI > > > Key: IMPALA-11915 > URL: https://issues.apache.org/jira/browse/IMPALA-11915 > Project: IMPALA > Issue Type: New Feature >Reporter: Quanlong Huang >Assignee: Surya Hebbar >Priority: Major > Labels: supportability > Fix For: Impala 4.3.0 > > Attachments: export_button.png, export_modal.png, > export_plan_example_70b4ecc5f6aec963e_85221a3b_plan.html, > export_timeline_example_0b4ecc5f6aec963e_85221a3b_timeline.svg, > exported_plan.png, exported_timeline.png, plan_download.png, > plan_download_button.png, plan_export.png, plan_export_modal.png, > plan_export_text_selection.png, svg_wrapped_export.html, text_selection.png, > timeline_download-1.png, timeline_download.png, timeline_download_button.png, > timeline_export.png, timeline_export_modal.png, > timeline_export_text_selection-1.png, timeline_export_text_selection.png > > > The graphical plan in the web UI is useful. It'd be nice to provide a button > to download the svg picture. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-12178) Refined alignment of timeticks in the webUI timeline
[ https://issues.apache.org/jira/browse/IMPALA-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quanlong Huang updated IMPALA-12178: Fix Version/s: Impala 4.3.0 > Refined alignment of timeticks in the webUI timeline > > > Key: IMPALA-12178 > URL: https://issues.apache.org/jira/browse/IMPALA-12178 > Project: IMPALA > Issue Type: Improvement >Reporter: Surya Hebbar >Assignee: Surya Hebbar >Priority: Minor > Fix For: Impala 4.3.0 > > Attachments: overflowed_timetick_label.png, timetick_label_fixed.png > > > The timeticks on the query timeline page in the WebUI were partially being > hidden due to the overflow for long timestamps after SVG rendering. > It would be better if the entire timtick label is displayed appropriately. > !overflowed_timetick_label.png|width=808,height=259! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-12182) Add CPU utilization time series graph for RuntimeProfile's sampled values
[ https://issues.apache.org/jira/browse/IMPALA-12182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quanlong Huang updated IMPALA-12182: Fix Version/s: Impala 4.3.0 > Add CPU utilization time series graph for RuntimeProfile's sampled values > - > > Key: IMPALA-12182 > URL: https://issues.apache.org/jira/browse/IMPALA-12182 > Project: IMPALA > Issue Type: New Feature >Reporter: Surya Hebbar >Assignee: Surya Hebbar >Priority: Major > Fix For: Impala 4.3.0 > > Attachments: 23-07-10_T15_33_44.png, 23-07-10_T15_36_26.png, > 23-07-10_T15_39_01.png, 23-07-10_T15_39_31.png, 23-07-10_T15_40_42.png, > 23-07-10_T15_40_50.png, 23-07-10_T15_40_55.png, cpu_utilization.png, > cpu_utilization_test-1.png, cpu_utilization_test-2.png, query_timeline.mkv, > simplescreenrecorder-2023-07-10_21.10.58.mkv, > simplescreenrecorder-2023-07-10_22.10.18.mkv, three_nodes.png, > three_nodes_zoomed_out.png, timeseries_cpu_utilization_line_plot.mkv, > two_nodes.png > > > The RuntimeProfile contains samples of CPU utilization metrics for user, sys > and iowait clamped to 64 values (retrieved from the ChunkedTimeSeriesCounter, > but sampled similar to SamplingTimeSeriesCounter). > It would be helpful to see the recent aggregate CPU node utilization samples > for each of the different nodes. > These are sampled every `periodic_counter_update_period_ms`. > AggregatedRuntimeProfile used in the Thrift profile contains the complete > series of values from the ChunkedTimeSeriesCounter samples. But, as this > representation is difficult to provide in the JSON, they have been > downsampled to 64 values. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-12364) Display disk and network metrics in webUI's query timeline
[ https://issues.apache.org/jira/browse/IMPALA-12364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quanlong Huang updated IMPALA-12364: Fix Version/s: Impala 4.4.0 > Display disk and network metrics in webUI's query timeline > -- > > Key: IMPALA-12364 > URL: https://issues.apache.org/jira/browse/IMPALA-12364 > Project: IMPALA > Issue Type: Improvement >Reporter: Surya Hebbar >Assignee: Surya Hebbar >Priority: Major > Fix For: Impala 4.4.0 > > Attachments: average_disk_network_metrics.mkv, > averaged_disk_network_metrics.png, both_charts_resize.mkv, > both_charts_resize.png, close_cpu_utilization_button.mkv, > draggable_resize_handle.png, hor_zoom_buttons.png, > horizontal_zoom_buttons.mkv, host_utilization_chart_resize.mkv, > host_utilization_close_button.png, host_utilization_resize_bar.png, > multiple_fragment_metrics.png, resize_drag_handle.mkv > > > It would be helpful to display disk and network usage in human readable form > on the query timeline, aligning it along with the CPU utilization plot, below > the fragment timing diagram. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-12886) Bump GoogleTest to 1.14.0 in the toolchain
[ https://issues.apache.org/jira/browse/IMPALA-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Gaal resolved IMPALA-12886. -- Resolution: Fixed https://github.com/cloudera/native-toolchain/commit/7daaa07f62a0ad4be1e98777d3e79c1ea60c92df IMPALA-12886: Bump GoogleTest version to 1.14.0 This is to unblock clang-tidy runs on ARM. The current version of gtest seems to suffer from a heap corruption problem that causes unpredictable segfaults in unified-be-tests. Upgrading to GoogleTest 1.14.0 fixed this problem in test runs, likely because previously existing global variables have been removed from GoogleTest's code. The patch removes the GOOGLETEST_VERSION specifier from the ORC library build, as unit tests are not built for it. Change-Id: Iaa52b4809a7c969e863518b182d2df63256f4c43 Reviewed-on: http://gerrit.cloudera.org:8080/21133 Tested-by: Laszlo Gaal Reviewed-by: Laszlo Gaal master > Bump GoogleTest to 1.14.0 in the toolchain > -- > > Key: IMPALA-12886 > URL: https://issues.apache.org/jira/browse/IMPALA-12886 > Project: IMPALA > Issue Type: Improvement > Components: Toolchain >Affects Versions: Impala 4.4.0 >Reporter: Laszlo Gaal >Assignee: Laszlo Gaal >Priority: Major > > The current toolchain version of GoogleTest (1.6.0) seems to cause problems > during clang-tidy runs happening in precommit test jobs. Recent local tests > showed the current version 1.14.0 to be free from this problem. v1.6.0 is > also more than 5 years old. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Reopened] (IMPALA-12886) Bump GoogleTest to 1.14.0 in the toolchain
[ https://issues.apache.org/jira/browse/IMPALA-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Gaal reopened IMPALA-12886: -- Track the Impala pickup in the same ticket. > Bump GoogleTest to 1.14.0 in the toolchain > -- > > Key: IMPALA-12886 > URL: https://issues.apache.org/jira/browse/IMPALA-12886 > Project: IMPALA > Issue Type: Improvement > Components: Toolchain >Affects Versions: Impala 4.4.0 >Reporter: Laszlo Gaal >Assignee: Laszlo Gaal >Priority: Major > > The current toolchain version of GoogleTest (1.6.0) seems to cause problems > during clang-tidy runs happening in precommit test jobs. Recent local tests > showed the current version 1.14.0 to be free from this problem. v1.6.0 is > also more than 5 years old. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-12886) Bump GoogleTest to 1.14.0
[ https://issues.apache.org/jira/browse/IMPALA-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Gaal updated IMPALA-12886: - Summary: Bump GoogleTest to 1.14.0 (was: Bump GoogleTest to 1.14.0 in the toolchain) > Bump GoogleTest to 1.14.0 > - > > Key: IMPALA-12886 > URL: https://issues.apache.org/jira/browse/IMPALA-12886 > Project: IMPALA > Issue Type: Improvement > Components: Toolchain >Affects Versions: Impala 4.4.0 >Reporter: Laszlo Gaal >Assignee: Laszlo Gaal >Priority: Major > > The current toolchain version of GoogleTest (1.6.0) seems to cause problems > during clang-tidy runs happening in precommit test jobs. Recent local tests > showed the current version 1.14.0 to be free from this problem. v1.6.0 is > also more than 5 years old. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Assigned] (IMPALA-12834) Add query load information to the query profile
[ https://issues.apache.org/jira/browse/IMPALA-12834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quanlong Huang reassigned IMPALA-12834: --- Assignee: YifanZhang > Add query load information to the query profile > --- > > Key: IMPALA-12834 > URL: https://issues.apache.org/jira/browse/IMPALA-12834 > Project: IMPALA > Issue Type: Improvement > Components: Perf Investigation >Reporter: YifanZhang >Assignee: YifanZhang >Priority: Minor > Fix For: Impala 4.4.0 > > > Add query load information to the query profile to track if the performance > regression is related to the insufficient resources of the node, and also > recommend if the current pool configurations or host configurations are > optimal. > The load information should include: > * Number of running queries of the executor group on which the query is > scheduled > * Number of running fragment instances of the hosts on which the query is > scheduled > * Used/Reserved memory of the hosts on which the query is scheduled > * Some other useful metrics -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org