You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Sandor Molnar (Jira)" <ji...@apache.org> on 2020/01/02 10:39:00 UTC
[jira] [Created] (KNOX-2157) Knox should check if it's actually
up&running
Sandor Molnar created KNOX-2157:
-----------------------------------
Summary: Knox should check if it's actually up&running
Key: KNOX-2157
URL: https://issues.apache.org/jira/browse/KNOX-2157
Project: Apache Knox
Issue Type: New Feature
Components: Server
Affects Versions: 1.3.0, 1.2.0, 1.1.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 1.4.0
As of now, Knox returns a success code in case the process is being created. There should be another way to check if the server is actually up&running and is capable of serving incoming requests.
My proposal is:
* the Knox startup script should be modified to run a basic Admin API check in case {{--test-gateway-url}} is defined in the startup command. If this is blank or non-defined we fallback to the existing PID-based check
* two more optional arguments will be defined for this feature:
** {{--test-gateway-retry-attempts}}: indicates the number of tries the startup script should execute before it fails. Defaults to 5.
** {{--test-gateway-retry-sleep}}: the amount of time that the test process will wait or sleep before a retry is issued. Defaults to 2s.
The new-style check will use {{curl}} and will return success in case {{$GATEWAY_TEST_URL/gateway/admin/api/v1/version/}} returns an HTTP response with code 200. If this is not true; the startup script should return an error code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)