[
https://issues.apache.org/jira/browse/AMBARI-20175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894946#comment-15894946
]
Sebastian Toader commented on AMBARI-20175:
-------------------------------------------
Committed to trunk:
{code}
commit f896b84116573c5432b60bdf90315edad20e61de
Author: Laszlo Puskas <[email protected]>
Date: Fri Mar 3 20:50:46 2017 +0100
AMBARI-20175. Rebalance HDFS operation returns after the command is issued.
(Laszlo Puskas via stoader)
{code}
Committed to branch-2.5:
{code}
commit d1d58ad8e931684b6d4a592026aa9f3f38eafdc2
Author: Laszlo Puskas <[email protected]>
Date: Fri Mar 3 21:00:57 2017 +0100
AMBARI-20175. Rebalance HDFS operation returns after the command is issued.
(Laszlo Puskas via stoader)
{code}
> 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.v4.patch, AMBARI-20175.trunk.v1.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)
