[
https://issues.apache.org/jira/browse/HCATALOG-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mithun Radhakrishnan updated HCATALOG-389:
------------------------------------------
Attachment: HCATALOG-389.patch
I've changed the #! to /usr/bin/env, and changed the variables names.
I've also suppressed the logging from the cleanup-function, since the messages
could be confusing.
> hcat_ping (script to check if HCatalog server is running/reachable)
> -------------------------------------------------------------------
>
> Key: HCATALOG-389
> URL: https://issues.apache.org/jira/browse/HCATALOG-389
> Project: HCatalog
> Issue Type: New Feature
> Components: client
> Affects Versions: 0.4.1
> Reporter: Mithun Radhakrishnan
> Assignee: Mithun Radhakrishnan
> Priority: Minor
> Fix For: 0.5
>
> Attachments: HCATALOG-389.patch
>
>
> It would be nice to have a script that checks if hcat_server is running,
> whether it's reachable and if it's "healthy". The current definition of
> "healthy" implies:
> 1. HCatalog responds to requests to list tables/databases.
> 2. Tables can be created/dropped in HCatalog.
> 3. When managed tables are used, table-directories are created/deleted on the
> DFS.
> 4. (Future:) ActiveMQ events are being posted correctly, when
> tables/partitions are created/dropped.
> Monitoring apps might use this script to detect when HCatalog is down.
> I'll post a trivial script that does 1-3, shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
