Skip to content

Manage metadata refresh logic in ClusterMetadata (via attached manager)#2920

Merged
dpkp merged 21 commits into
masterfrom
dpkp/cluster-manages-metadata
Apr 26, 2026
Merged

Manage metadata refresh logic in ClusterMetadata (via attached manager)#2920
dpkp merged 21 commits into
masterfrom
dpkp/cluster-manages-metadata

Conversation

@dpkp
Copy link
Copy Markdown
Owner

@dpkp dpkp commented Apr 26, 2026

  • Use long running async loop for metadata refresh
  • cluster runs loop
  • Move refresh/loop -> cluster (wip)
  • bootstrap_async
  • Fixup wakeup/notify; catch exceptions
  • manager fixture
  • Fixup cluster request_update calls
  • use manager.send not conn.send_request in refresh_metadata
  • Move TestKafkaConnectionManagerMetadataRefresh -> test_cluster.py
  • use cluster fixture
  • Fix test_bootstrap_retries_empty_brokers
  • modify bootstrap logging
  • ClusterMetadata.attach(manager)
  • Unify metadata_refresh_in_progress handling
  • No return from refresh_metadata
  • longer timeout for request_update send test
  • weakref attach; use self._manager
  • Use refresh_future to track metadata in progress; protect concurrent access to refresh_metadata

@dpkp dpkp merged commit 9552948 into master Apr 26, 2026
19 checks passed
@dpkp dpkp deleted the dpkp/cluster-manages-metadata branch April 26, 2026 01:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant