jaegertracing/jaeger

Add Cassandra in healthcheck

Open

#633 opened on Jan 4, 2018

View on GitHub
 (10 comments) (5 reactions) (0 assignees)Go (18,974 stars) (2,326 forks)batch import
enhancementhelp wanted

Description

We are observing a strange issue where both Query and Collector does not reconnect to the Cassandra cluster and both logs "gocql: no hosts available in the pool"

The problem seems to be either with GoCQL or with our setup, but I think that Query and Collector healthcheck should reflect that as a problem.

As of now, killing the pods were enough to fix the issue.

Contributor guide

Tech stack
go
Domain
backendobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingJaeger architectureCassandra basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue proposes adding a healthcheck endpoint for Cassandra connectivity in Jaeger's Query and Collector components. Relevant files might include healthcheck handlers in `cmd/query/` and `cmd/collector/` directories. The issue comments may provide additional context on the observed failure and expected behavior. A maintainer could clarify the preferred approach for monitoring Cassandra connections.