Skip to content

Upstream 2041 - Close idle Valkey connections - #25

Merged
cigamit merged 1 commit into
ctrliq:develfrom
blaipr:fix/valkey-idle-timeout
Aug 20, 2026
Merged

cigamit merged 1 commit into
ctrliq:develfrom
blaipr:fix/valkey-idle-timeout

Conversation

@blaipr

@blaipr blaipr commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Upstream PR: ansible/awx-operator#2041

SUMMARY

The valkey_conf block generated by roles/installer/templates/configmaps/config.yaml.j2 sets no timeout, so Valkey keeps idle client connections open indefinitely. On long-running instances they accumulate until the server starts refusing new ones with ERR max number of clients reached.

Upstream applies it to the equivalent redis_conf block; timeout is a Redis directive Valkey retains, so it carries over unchanged.

For reference, the block as it stands is upstream's minus that one line:

unixsocket /var/run/valkey/valkey.sock
unixsocketperm 777
port 0
bind 127.0.0.1

Not present in this fork.

ISSUE TYPE
  • Bug, Docs Fix or other nominal change
COMPONENT NAME
  • Other (installer role templates)

The generated valkey.conf set no timeout, so Valkey never reclaimed idle
client connections and long-running instances accumulated them until
reaching maxclients.

Ports ansible/awx-operator#2041.
@blaipr blaipr changed the title Close idle Valkey connections Upstream 2041 - Close idle Valkey connections Aug 12, 2026
@cigamit cigamit self-assigned this Aug 20, 2026
@cigamit cigamit added the bug Something isn't working label Aug 20, 2026
@cigamit
cigamit merged commit bd192d3 into ctrliq:devel Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Development

Successfully merging this pull request may close these issues.

2 participants