Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

WAL makes memory full due to SAS token expiration

Open
#941 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
azure, go, postgresql
Domain
cloud, databases

Research direction

No files or tests are named in the issue. Start by reproducing an expired Azure SAS token with CNPG 1.26 and Barman plugin 0.11.0, then inspect WAL retention and recovery after the token is updated. Done means queued WALs are released after credential recovery without requiring a memory increase.

Written by the indexing model from the issue text.

Description

bug

I am using CNPG 1.26 with Barman plugin 0.11.0 . I am taking backup on azure blob storage. I am using SAS token to connect with azure blob storage . But when SAS token expire and I forgot to update it . after that it looks like it stores wals inside pods memory which increases memory consumption which results it into pod not working. But After I update sas token it should release wal and make memory free. but it did not happen. It deletes the wal only after increasing the db cluster memory . Is there any other way to resolve this issue or release this memory.

@dosu, please help

Dominant language
Go
Stars
192
Forks
75
Avg merge
1d 7h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

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 cloudnative-pg/plugin-barman-cloud

All issues in cloudnative-pg/plugin-barman-cloud

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.