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

Hadoop QA commented on AMBARI-20175:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12855158/AMBARI-20175.b-2.5.scripttimeout.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10807//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10807//console

This message is automatically generated.

> Rebalance HDFS operation returns after the command is issued
> ------------------------------------------------------------
>
>                 Key: AMBARI-20175
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20175
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Laszlo Puskas
>            Assignee: Laszlo Puskas
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20175.b-2.5.scripttimeout.patch, 
> AMBARI-20175.b-2.5.v2.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The rebalancing operation may take a long time (hours, days) thus when issued 
> from the ambari UI the background operation may time out.
> As it's not possible to dynamically predict how long the rebalancing will 
> last , the approach taken by this solution is to only trigger the operation 
> and not wait to the operation to finish. 
> (Worths mentioning here, that after this change the progress of the rebalance 
> operation won't be tracked anymore in the background operation; also the user 
> won't be notified about the success/failure of the operation)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to