I am consistently seeing an issues where a custom service is started and the status of the service is marked as running, even though service is still not available.
Here are the commands I am issuing:
- start service
curl -w'\n' -X POST $CDAP_URL/namespaces/default/apps/ConfigApp/services/ConfigService/start
- check status
- Invoke service
curl -w'\n' -X GET $CDAP_URL/namespaces/default/apps/ConfigApp/services/ConfigService/methods/config
No discoverable found for request : /v3/namespaces/default/apps/ConfigApp/services/ConfigService/methods/config
I am issuing these commands from a script, so to get around the issue I have to add a sleep before I invoke the service.