You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Jeffrey Hagelberg (JIRA)" <ji...@apache.org> on 2016/12/16 20:14:58 UTC

[jira] [Comment Edited] (ATLAS-1389) Ping REST API entrypoint

    [ https://issues.apache.org/jira/browse/ATLAS-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15755412#comment-15755412 ] 

Jeffrey Hagelberg edited comment on ATLAS-1389 at 12/16/16 8:14 PM:
--------------------------------------------------------------------

[~yhemanth] - The admin/status API did not exist when we implemented this.  It probably makes sense for the logic to become part of that endpoint.  Basically, the additional information that it provides is an estimate of the round trip time to the backend database.  It also validates that a trivial gremlin query can be executed successfully.  It takes a parameter that specifies the number of pings to do.  Let's discuss this when we are ready to start working on this JIRA.


was (Author: jnhagelb):
[~yhemanth] - The admin/status API did not exist when we implemented this.  It probably makes sense for the logic to become part of that endpoint.  Basically, the additional information that it provides is an estimate of the round trip time to the backend database.  It takes a parameter that specifies the number of pings to do.  Let's discuss this when we are ready to start working on this JIRA.

> Ping REST API entrypoint
> ------------------------
>
>                 Key: ATLAS-1389
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1389
>             Project: Atlas
>          Issue Type: New Feature
>            Reporter: David Kantor
>            Assignee: Jeffrey Hagelberg
>
> Provide a lightweight ping API to allow clients to check status of Atlas server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)