[
https://issues.apache.org/jira/browse/AMBARI-20175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883215#comment-15883215
]
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/12854511/AMBARI-20175.b-2.5.v2.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10742//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.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)
