ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20175) Rebalance HDFS operation returns after the command is issued
Date Fri, 03 Mar 2017 20:45:46 GMT

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

Hudson commented on AMBARI-20175:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6940 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6940/])
AMBARI-20175. Rebalance HDFS operation returns after the command is (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f896b84116573c5432b60bdf90315edad20e61de])
* (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/namenode.py
* (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/hdfs_rebalance.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
* (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_rebalance.py


> 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)

Mime
View raw message