[
https://issues.apache.org/jira/browse/AURORA-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097894#comment-14097894
]
Erik van Roode commented on AURORA-653:
---------------------------------------
Over time the number of actual instances actually running can go up and down,
but with the existing behavior I have no way of telling whether someone ran
aurora update with a new value, or whether jobs died and aren't restarting. The
former case is OK, the latter is bad and worthy of someones attention. You'd
need to know what the number of instances set by the most recent update is to
be able to distinguish the two cases. I would expect to always see the
"instances" as set by the most recent update.
"instances running" can come from a number of places, eg getJobSummary
pendingTaskCount activeTaskCount finishedTaskCount failedTaskCount
Those are the numbers the scheduler UI seems to display
There's a few other places where numbers pop up but struct JobStats seems to be
the best source.
> Make Job.instances value available through the IDL
> --------------------------------------------------
>
> Key: AURORA-653
> URL: https://issues.apache.org/jira/browse/AURORA-653
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Erik van Roode
>
> Why:
> I would like to be able to determine the health of an app, as in the ratio
> of how many instances are running
> and how many instances were configured to run (Job.instances).
> I can find the "Active" number in various places, but I cannot find the
> "Configured" anywhere.
> As far as I can tell every instance of "Instances/instanceCount" is actually
> the number of active jobs/tasks.
> Eg, JobConfiguration contains instanceCount, but it is not Job.instances.
> I created a job with 5 instances,
> killed one, and instanceCount dropped to 4.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
