You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Mark Chu-Carroll (JIRA)" <ji...@apache.org> on 2014/05/11 00:10:18 UTC
[jira] [Created] (AURORA-400) Restart generates incorrect error
message when called with invalid instances
Mark Chu-Carroll created AURORA-400:
---------------------------------------
Summary: Restart generates incorrect error message when called with invalid instances
Key: AURORA-400
URL: https://issues.apache.org/jira/browse/AURORA-400
Project: Aurora
Issue Type: Bug
Components: Client
Reporter: Mark Chu-Carroll
Assignee: Mark Chu-Carroll
This is a weird edge case but I've typo'd jobs enough to notice it a few times.
{code:borderStyle=solid}
$ aurora restart test/user/prod/service --shards=235
INFO] Performing rolling restart of job test/user/prod/service (instances: [235])
INFO] Restarting instances: [235]
ERROR] Error restarting instances: Not all requested shards are active.
INFO] Response from scheduler: INVALID_REQUEST (message: Not all requested shards are active.)
{code}
Note that job test/user/prod/service doesn't exist, though the error doesn't call that out. Instead, one is lead to believe that the typo lie merely in the shard id specified
A bare restart on non-existent job for contrast:
{code:borderStyle=solid}
$ aurora restart test/user/prod/service
INFO] Response from scheduler: INVALID_REQUEST (message: No tasks found for query: TaskQuery(owner:Identity(role:user, user:null), environment:prod, jobName:user-service-production, taskIds:null, statuses:[PREEMPTING, RESTARTING, DRAINING, RUNNING, ASSIGNED, KILLING, STARTING, THROTTLED, PENDING], slaveHost:null, instanceIds:null))
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)