github.com/huiliang/nomad@v0.2.1-0.20151124023127-7a8b664699ff/website/source/docs/commands/alloc-status.html.md.erb (about)

     1  ---
     2  layout: "docs"
     3  page_title: "Commands: alloc-status"
     4  sidebar_current: "docs-commands-alloc-status"
     5  description: >
     6    Display status and metadata about existing allocations and their tasks.
     7  ---
     8  
     9  # Command: alloc-status
    10  
    11  The `alloc-status` command displays status information and metadata about an
    12  existing allocation and its tasks. It can be useful while debugging to reveal
    13  the underlying reasons for scheduling decisions or failures, as well as the
    14  current state of its tasks.
    15  
    16  ## Usage
    17  
    18  ```
    19  nomad alloc-status [options] <allocation>
    20  ```
    21  
    22  An allocation ID must be provided. This specific allocation will be queried
    23  and detailed information for it will be dumped.
    24  
    25  ## General Options
    26  
    27  <%= general_options_usage %>
    28  #
    29  ## Status Options
    30  
    31  * `-short`: Display short output. Shows only the most recent task event.
    32  
    33  ## Examples
    34  
    35  Short status of an alloc:
    36  
    37  ```
    38  $ nomad alloc-status --short a7365fe4-8b9f-4284-612d-a101fb41e773
    39  ID                = a7365fe4-8b9f-4284-612d-a101fb41e773
    40  EvalID            = 44c2d9ed-6377-ca3d-14a8-b2e6327230ce
    41  Name              = example.cache[0]
    42  NodeID            = e55859b1-4330-f00b-da49-8a292432ead3
    43  JobID             = example
    44  ClientStatus      = running
    45  NodesEvaluated    = 1
    46  NodesFiltered     = 0
    47  NodesExhausted    = 0
    48  AllocationTime    = 911.026µs
    49  CoalescedFailures = 0
    50  redis
    51  web
    52  
    53  ==> Tasks
    54  Name   State    LastEvent  Time
    55  redis  running  Started    02:29:40 11/17/15
    56  web    running  Started    02:30:41 11/17/15
    57  
    58  ==> Status
    59  Allocation "a7365fe4-8b9f-4284-612d-a101fb41e773" status "running" (0/1 nodes filtered)
    60    * Score "e55859b1-4330-f00b-da49-8a292432ead3.binpack" = 10.334026
    61  ```
    62  
    63  Full status of an alloc, which shows one of the tasks dying and then being restarted:
    64  
    65  ```
    66  $ nomad alloc-status a7365fe4-8b9f-4284-612d-a101fb41e773
    67  ID                = a7365fe4-8b9f-4284-612d-a101fb41e773
    68  EvalID            = 44c2d9ed-6377-ca3d-14a8-b2e6327230ce
    69  Name              = example.cache[0]
    70  NodeID            = e55859b1-4330-f00b-da49-8a292432ead3
    71  JobID             = example
    72  ClientStatus      = running
    73  NodesEvaluated    = 1
    74  NodesFiltered     = 0
    75  NodesExhausted    = 0
    76  AllocationTime    = 911.026µs
    77  CoalescedFailures = 0
    78  
    79  ==> Task "redis" is "running"
    80  Recent Events:
    81  Time               Type     Description
    82  02:29:40 11/17/15  Started  <none>
    83  
    84  ==> Task "web" is "running"
    85  Recent Events:
    86  Time               Type        Description
    87  02:30:41 11/17/15  Started     <none>
    88  02:30:02 11/17/15  Terminated  Exit Code: 137, Exit Message: "Docker container exited with non-zero exit code: 137"
    89  02:29:40 11/17/15  Started     <none>
    90  
    91  ==> Status
    92  Allocation "a7365fe4-8b9f-4284-612d-a101fb41e773" status "running" (0/1 nodes filtered)
    93    * Score "e55859b1-4330-f00b-da49-8a292432ead3.binpack" = 10.334026
    94  
    95  ```