Kam Kasravi created GEARPUMP-83:
-----------------------------------
Summary: After killing all worker instances, application status
should not be described as active
Key: GEARPUMP-83
URL: https://issues.apache.org/jira/browse/GEARPUMP-83
Project: Apache Gearpump
Issue Type: Bug
Components: Dashboard
Affects Versions: 0.8.0
Reporter: Kam Kasravi
Priority: Minor
Fix For: 0.8.1
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:
{code}
{"appMasters":[{"status":"active","appId":1,"appName":"dag","appMasterPath":"akka.tcp://[email protected]:46761/user/daemon/appdaemon1/$c","workerPath":"akka.tcp://[email protected]:59201/user/Worker48a47aa6-81c0-493c-9948-9d7d4c946db6","submissionTime":"1451894551477","startTime":"1451894553568","user":"qxu"},{"status":"active","appId":2,"appName":"wordCount","appMasterPath":"akka.tcp://[email protected]:49261/user/daemon/appdaemon2/$c","workerPath":"akka.tcp://[email protected]:59201/user/Worker48a47aa6-81c0-493c-9948-9d7d4c946db6","submissionTime":"1451898038991","startTime":"1451898040265","user":"qxu"}]}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
