jaegertracing/jaeger

Add Cassandra in healthcheck

Open

#633 opened on Jan 4, 2018

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

Repository metrics

Stars
 (18,974 stars)
PR merge metrics
 (Avg merge 4d 11h) (85 merged PRs in 30d)

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

Research direction
Implement a healthcheck endpoint for Cassandra in the Query and Collector components to detect connection issues like 'gocql: no hosts available in the pool'.
Tech stack
go
Domain
database
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65