hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-18203) change the way WM is enabled and allow dropping the last resource plan
Date Sat, 09 Dec 2017 12:15:04 GMT

    [ https://issues.apache.org/jira/browse/HIVE-18203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284713#comment-16284713
] 

Hive QA commented on HIVE-18203:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12901270/HIVE-18203.01.patch

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/8160/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/8160/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-8160/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Tests exited with: ExecutionException: java.util.concurrent.ExecutionException: org.apache.hive.ptest.execution.ssh.SSHExecutionException:
RSyncResult [localFile=/data/hiveptest/logs/PreCommit-HIVE-Build-8160/succeeded/18-TestCliDriver-list_bucket_dml_1.q-ppd_join3.q-auto_join23.q-and-27-more,
remoteFile=/home/hiveptest/35.184.14.247-hiveptest-0/logs/, getExitCode()=255, getException()=null,
getUser()=hiveptest, getHost()=35.184.14.247, getInstance()=0]: 'Warning: Permanently added
'35.184.14.247' (ECDSA) to the list of known hosts.
receiving incremental file list
./
TEST-18-TestCliDriver-list_bucket_dml_1.q-ppd_join3.q-auto_join23.q-and-27-more-TEST-org.apache.hadoop.hive.cli.TestCliDriver.xml

              0   0%    0.00kB/s    0:00:00  
        114,519 100%    1.61MB/s    0:00:00 (xfr#1, to-chk=5/7)
maven-test.txt

              0   0%    0.00kB/s    0:00:00  
         56,493 100%  540.87kB/s    0:00:00 (xfr#2, to-chk=4/7)
logs/
logs/derby.log

              0   0%    0.00kB/s    0:00:00  
         39,894 100%  284.37kB/s    0:00:00 (xfr#3, to-chk=1/7)
logs/hive.log

              0   0%    0.00kB/s    0:00:00  
      1,966,080   2%    1.83MB/s    0:00:41  
      8,585,216  10%    4.04MB/s    0:00:16  
     25,690,112  32%    8.10MB/s    0:00:06  Timeout, server 35.184.14.247 not responding.

rsync: connection unexpectedly closed (55496090 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [receiver=3.1.1]
rsync: connection unexpectedly closed (428 bytes received so far) [generator]
rsync error: unexplained error (code 255) at io.c(226) [generator=3.1.1]
ssh: connect to host 35.184.14.247 port 22: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1]
ssh: connect to host 35.184.14.247 port 22: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1]
ssh: connect to host 35.184.14.247 port 22: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1]
ssh: connect to host 35.184.14.247 port 22: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1]
'
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12901270 - PreCommit-HIVE-Build

> change the way WM is enabled and allow dropping the last resource plan
> ----------------------------------------------------------------------
>
>                 Key: HIVE-18203
>                 URL: https://issues.apache.org/jira/browse/HIVE-18203
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Aswathy Chellammal Sreekumar
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-18203.01.patch, HIVE-18203.patch
>
>
> Currently it's impossible to drop the last active resource plan even if WM is disabled.
It should be possible to deactivate the last resource plan AND disable WM in the same action.
Activating a resource plan should enable WM in this case.
> This should interact with the WM queue config in a sensible manner.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message