jaegertracing/jaeger

Add Cassandra in healthcheck

Open

#633 创建于 2018年1月4日

在 GitHub 查看
 (10 评论) (5 反应) (0 负责人)Go (18,974 star) (2,326 fork)batch import
enhancementhelp wanted

描述

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.

贡献者指南

技术栈
go
领域
backendobservability
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Go programmingJaeger architectureCassandra basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
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.