Skip to content

Bump kafka_ex from 1.1.0 to 1.1.1 - #274

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/hex/kafka_ex-1.1.1
Open

Bump kafka_ex from 1.1.0 to 1.1.1#274
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/hex/kafka_ex-1.1.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 27, 2026

Copy link
Copy Markdown
Contributor

Bumps kafka_ex from 1.1.0 to 1.1.1.

Release notes

Sourced from kafka_ex's releases.

v1.1.1

What's Changed

Fixes memory leak on client tracking all topics

Full Changelog: kafkaex/kafka_ex@v1.1.0...v1.1.1

Changelog

Sourced from kafka_ex's changelog.

1.1.1 (2026-07-24)

Fixed

  • Client tracks metadata only for topics it actually uses. Previously the periodic refresh folded every topic ever seen into one request and health-gated the whole set, absorbing the entire cluster catalog and never pruning it — so one deleted topic stormed :error logs every cycle and discarded the whole refresh, including fresh leader data for in-use topics (a liveness bug). The client now refreshes only used topics, merges whatever it gets, and logs unavailable used topics edge-triggered (:warning/:info) instead of :error every cycle. Behavior change: the catalog is no longer kept warm; first use of a new topic costs one metadata fetch.

  • Metadata refresh no longer stalls the client on a deleted-but-tracked topic. A permanently missing tracked topic re-ran the full retry ladder (~600ms of sleeps) inside the client on every refresh; the retry-sleep now runs only the first time a topic goes missing. Known limitation: the tracked-topic set is not yet pruned, so an ever-growing set of distinct topic names accumulates for the client's lifetime; pruning is planned.

  • A consumer that starts its own client scopes it to its own topic. A GenConsumer with no shared :client now seeds the client it starts with initial_topics: [topic], so its first metadata refresh covers just that topic instead of the whole cluster catalog — avoiding N simultaneous whole-catalog fetches at group startup.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [kafka_ex](https://github.com/kafkaex/kafka_ex) from 1.1.0 to 1.1.1.
- [Release notes](https://github.com/kafkaex/kafka_ex/releases)
- [Changelog](https://github.com/kafkaex/kafka_ex/blob/master/CHANGELOG.md)
- [Commits](kafkaex/kafka_ex@v1.1.0...v1.1.1)

---
updated-dependencies:
- dependency-name: kafka_ex
  dependency-version: 1.1.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file elixir Pull requests that update elixir code labels Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file elixir Pull requests that update elixir code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants