Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retry for failed operation #158

Merged
merged 53 commits into from
Aug 20, 2024
Merged

Retry for failed operation #158

merged 53 commits into from
Aug 20, 2024

Conversation

kmrdhruv
Copy link
Collaborator

Initial implementation of retry failed operation in controller. Retry is based on simple retry policy and will always be attempted. Currently retry is failure agnostic.

TODO:: working on tests.

…ution and updates on subscription operation for a subscription
…criptions. This includes

- main sub, retry topic & sub, dlt topic & sub
- basic shard/partitioning based on qps/throughput limits
- subscription running status controller API
- subscription provisioning status in rest API
Moved internal queue type and topic partition related entities to entities module.
- Add active produce/consume topic/subscription to composite entities
- Move default topic/node capacity to config from hard coded values.
- moved varadhitopic factory/service to server module.
- refactoring related to start subscription in consumer
Copy link

github-actions bot commented Jul 22, 2024

Test Results

280 tests   280 ✅  59s ⏱️
 55 suites    0 💤
 55 files      0 ❌

Results for commit c3858ff.

♻️ This comment has been updated with latest results.

import lombok.AllArgsConstructor;

@AllArgsConstructor
public class RetryPolicy {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can use builder with defaults here to allow easy construction of the instance

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not doing this for now as not sure of final policy struct, also policy is created only once in code (excluding test). Would prefer to avoid test defaults in prod code.

@kmrdhruv kmrdhruv merged commit 62b274b into master Aug 20, 2024
3 checks passed
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.

2 participants