ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandor Magyari (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-14360) Ambari API: request tasks are not returned via API
Date Sun, 13 Dec 2015 15:01:46 GMT

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

Sandor Magyari updated AMBARI-14360:
------------------------------------
    Description: 
In case of provisioning a cluster via Blueprints API, tasks are not returned for Topology
Logical Request.

In the below example, you can see that the request specifies that there are 40 tasks and 40
completed tasks but there are no task sub-resources returned.
{code}
GET http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1
{code}
returns
{code}
{
  "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1",
  "Requests" : {
    "aborted_task_count" : 0,
    "cluster_name" : "c1",
    "completed_task_count" : 40,
    "create_time" : 1448413081566,
    "end_time" : -1,
    "exclusive" : false,
    "failed_task_count" : 0,
    "id" : 1,
    "inputs" : null,
    "operation_level" : null,
    "progress_percent" : 100.0,
    "queued_task_count" : 0,
    "request_context" : "Logical Request: Provision Cluster 'c1'",
    "request_schedule" : null,
    "request_status" : "COMPLETED",
    "resource_filters" : null,
    "start_time" : -1,
    "task_count" : 40,
    "timed_out_task_count" : 0,
    "type" : null
  },
  "stages" : [
    {
      "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1/stages/1",
      "Stage" : {
        "cluster_name" : "c1",
        "request_id" : 1,
        "stage_id" : 1
      }
    }
  ],
  "tasks" : [ ]
}
{code}

When asking specifically for the tasks resource, it returns an empty set even though there
are actually 40 tasks associated with the request.
{code}
{
  "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1/tasks",
  "items" : [ ]
}
{code}

  was:
In the below example, you can see that the request specifies that there are 40 tasks and 40
completed tasks but there are no task sub-resources returned.
{code}
GET http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1
{code}
returns
{code}
{
  "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1",
  "Requests" : {
    "aborted_task_count" : 0,
    "cluster_name" : "c1",
    "completed_task_count" : 40,
    "create_time" : 1448413081566,
    "end_time" : -1,
    "exclusive" : false,
    "failed_task_count" : 0,
    "id" : 1,
    "inputs" : null,
    "operation_level" : null,
    "progress_percent" : 100.0,
    "queued_task_count" : 0,
    "request_context" : "Logical Request: Provision Cluster 'c1'",
    "request_schedule" : null,
    "request_status" : "COMPLETED",
    "resource_filters" : null,
    "start_time" : -1,
    "task_count" : 40,
    "timed_out_task_count" : 0,
    "type" : null
  },
  "stages" : [
    {
      "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1/stages/1",
      "Stage" : {
        "cluster_name" : "c1",
        "request_id" : 1,
        "stage_id" : 1
      }
    }
  ],
  "tasks" : [ ]
}
{code}

When asking specifically for the tasks resource, it returns an empty set even though there
are actually 40 tasks associated with the request.
{code}
{
  "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1/tasks",
  "items" : [ ]
}
{code}


> Ambari API: request tasks are not returned via API
> --------------------------------------------------
>
>                 Key: AMBARI-14360
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14360
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>            Priority: Critical
>             Fix For: 2.2.0
>
>
> In case of provisioning a cluster via Blueprints API, tasks are not returned for Topology
Logical Request.
> In the below example, you can see that the request specifies that there are 40 tasks
and 40 completed tasks but there are no task sub-resources returned.
> {code}
> GET http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1
> {code}
> returns
> {code}
> {
>   "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1",
>   "Requests" : {
>     "aborted_task_count" : 0,
>     "cluster_name" : "c1",
>     "completed_task_count" : 40,
>     "create_time" : 1448413081566,
>     "end_time" : -1,
>     "exclusive" : false,
>     "failed_task_count" : 0,
>     "id" : 1,
>     "inputs" : null,
>     "operation_level" : null,
>     "progress_percent" : 100.0,
>     "queued_task_count" : 0,
>     "request_context" : "Logical Request: Provision Cluster 'c1'",
>     "request_schedule" : null,
>     "request_status" : "COMPLETED",
>     "resource_filters" : null,
>     "start_time" : -1,
>     "task_count" : 40,
>     "timed_out_task_count" : 0,
>     "type" : null
>   },
>   "stages" : [
>     {
>       "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1/stages/1",
>       "Stage" : {
>         "cluster_name" : "c1",
>         "request_id" : 1,
>         "stage_id" : 1
>       }
>     }
>   ],
>   "tasks" : [ ]
> }
> {code}
> When asking specifically for the tasks resource, it returns an empty set even though
there are actually 40 tasks associated with the request.
> {code}
> {
>   "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1/tasks",
>   "items" : [ ]
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message