HA setup, inactive icingadb-redis keeps growing

Open
#1,122 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
go, redis
Domain
backend, databases, distributed-systems

Research direction

Reproduce the two-node Icinga2/IcingaDB HA setup with Redis A and B, then compare dump.rdb and memory usage while each node is active or inactive. Trace the HA and Redis handling in IcingaDB v1.5.1; done means determining whether the growth is expected and defining a verified fix or manual-switch behavior.

Written by the indexing model from the issue text.

Description

Setup:
Icinga2 master A ( HA ) -> IcingaDB A ( HA ) -> Redis A
Icinga2 master B ( HA ) -> IcingaDB B ( HA ) -> Redis B

Icinga DB version: v1.5.1
Redis server v=8.2.6

Issue:
Dump file ( dump.rdb ) and memory usage of Redis database on server with inactive IcingaDB node keeps growing significantly. Active IcingaDB instance keeps size of dump file and memory usage of Redis database within 'normal' values.

For example:
Redis A 2MB
Redis B 400MB

After force switch of active IcingaDB node A to node B dump file size is reduced to 2MB as well. But, A will start growing.

Is it normal behavior? If yes, is it possible to implement command for manual switch of active node?

Dominant language
Go
Stars
76
Forks
23
Avg merge
13h 37m
Merged PRs (30d)
11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Icinga/icingadb

All issues in Icinga/icingadb

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.