[GEARPUMP-83] After killing all worker instances, application status should not be described as active

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.8.0
• Fix Version/s: 0.8.1
• Component/s: services
• Assignee: Manu Zhang
• Reporter: Kam Kasravi
• Created: 21/Apr/16 13:34
• Updated: 03/Jun/16 01:22
• Resolved: 03/Jun/16 01:22

Description

Step to reproduce:

Start cluster with one worker
Start a word count
Kill the worker
Expect /api/v1.0/master/applist actually returns app status as active, but application's detail page is not available. I think as there is no resource to run the application, the application is in some abnormal status. In order not to mislead user, I think we should invent a new status, might be recovering or something.

Example output:

{"appMasters":[{"status":"active","appId":1,"appName":"dag","appMasterPath":"akka.tcp://app1-executor-1@127.0.0.1:46761/user/daemon/appdaemon1/$c","workerPath":"akka.tcp://48a47aa6-81c0-493c-9948-9d7d4c946db6@127.0.0.1:59201/user/Worker48a47aa6-81c0-493c-9948-9d7d4c946db6","submissionTime":"1451894551477","startTime":"1451894553568","user":"qxu"},{"status":"active","appId":2,"appName":"wordCount","appMasterPath":"akka.tcp://app2-executor-1@127.0.0.1:49261/user/daemon/appdaemon2/$c","workerPath":"akka.tcp://48a47aa6-81c0-493c-9948-9d7d4c946db6@127.0.0.1:59201/user/Worker48a47aa6-81c0-493c-9948-9d7d4c946db6","submissionTime":"1451898038991","startTime":"1451898040265","user":"qxu"}]}

Issue Links

• links to: GitHub Pull Request #31