ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laszlo Puskas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-20175) Rebalance HDFS operation returns after the command is issued
Date Mon, 20 Mar 2017 12:43:41 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-20175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Laszlo Puskas updated AMBARI-20175:
-----------------------------------
    Description: 
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 for 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)

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


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