Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • P Partition
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Partition
  • Issues
  • #10
Closed
Open
Issue created May 05, 2021 by Mingyang Zhu@mzhu9Maintainer

Customized readiness check API

We'd like to use spring boot built-in actuator health endpoint for the partition service health check API, and implement a customized health indicator.

Partition service implements the cache layer, different cloud provider's implementation implements the cache differently. It will be good to make sure the cache infrastructure and connection are ready before the pod serves the traffic.

To achieve this, the service will implement the custom health indicator, and get a dummy key from the cache instance. No matter it is memcache, redis, it expects no exception to claim the pod is ready to serve the traffic. This health check can be enabled or disabled by the configuration.

Edited May 19, 2021 by Mingyang Zhu
Assignee
Assign to
Time tracking