You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/08/08 00:01:49 UTC
[jira] [Created] (AMBARI-2838) Running Requests are not visibile on
the UI since the API is not returning the running requests.
Sumit Mohanty created AMBARI-2838:
-------------------------------------
Summary: Running Requests are not visibile on the UI since the API is not returning the running requests.
Key: AMBARI-2838
URL: https://issues.apache.org/jira/browse/AMBARI-2838
Project: Ambari
Issue Type: Bug
Components: controller
Affects Versions: 1.2.5
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Fix For: 1.2.5
The issue is the following:
getRequestsByTaskStatus behaves correctly and returns the latest N requests. Note that the N requests have M (M >> N) tasks.
Then the call to findByRequestIds gets oldest N tasks where the requestId for tasks belong to the list returned by the first call. So instead of getting M tasks we only get N tasks that too N oldest tasks which are returned. As a result the call never returns that latest request/tasks.
The fix is to drop the filter done by the calls findByRequestIds and findByRequestAndTaskIds. Filter should only be applied on the number of requests to be returned.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira