Skip to content

Conversation

@loserwang1024
Copy link
Contributor

Purpose

Linked issue: close #288

Inspired by https://issues.apache.org/jira/browse/KAFKA-12609, which introduce AdminApiDriver do theses things:

  • Retry lookup stage on receiving NOT_LEADER_OR_FOLLOWER and LEADER_NOT_AVAILABLE, whereas in the past we failed the partition directly without retry.

  • retry fulfillment stage on RetriableException

Tests

  • AdminApiDriverTest for AdminApiDriver
  • com.alibaba.fluss.client.admin.FlussAdminITCase#testListOffsets for Admin#ListOffsets

API and Format

Some internal interface:

  • AdminApiDriver
  • AdminApiHandler
  • AdminApiFuture
  • AdminApiLookupBrokerIdStrategy

Documentation

@loserwang1024
Copy link
Contributor Author

@swuferhong
Copy link
Contributor

@loserwang1024 The branch has conflicts.

@loserwang1024 loserwang1024 force-pushed the AdminApiDriver branch 2 times, most recently from 52a2c01 to fd550fe Compare March 6, 2025 07:17
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.

[Bug] New Partiions created will cause Flink job failover when partition discovery is enabled while scanning

2 participants