[ https://issues.apache.org/jira/browse/IMPALA-13031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842850#comment-17842850 ]
ASF subversion and git services commented on IMPALA-13031: ---------------------------------------------------------- Commit 5b70e48ebbaac234338f2077ce6505f35b2d37aa in impala's branch refs/heads/master from Yida Wu [ https://gitbox.apache.org/repos/asf?p=impala.git;h=5b70e48eb ] IMPALA-13031: Enhancing logging for spilling configuration with local buffer directory details The patch adds logging for local buffer directory when using remote scratch space. The printed log would be like "Using local buffer directory for scratch space /tmp/test/impala-scratch on disk 8 limit: 500.00 MB, priority: 2147483647". Tests: Manally tests the logging working as described. Change-Id: I8fb357016d72a363ee5016f7881b0f6b0426aff5 Reviewed-on: http://gerrit.cloudera.org:8080/21350 Reviewed-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com> > Enhancing logging for spilling configuration with local buffer directory > details > -------------------------------------------------------------------------------- > > Key: IMPALA-13031 > URL: https://issues.apache.org/jira/browse/IMPALA-13031 > Project: IMPALA > Issue Type: Improvement > Components: Backend > Reporter: Yida Wu > Assignee: Yida Wu > Priority: Major > > When setting up spilling to a remote location, it also needs to configure a > local buffer directory within the scratch directories. However, the current > logging does not include any information about the local buffer directory, > such as its capacity or other relevant details. It would be beneficial to log > this information for better tracking of potential issues. -- 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