Skip to content
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.

[scheduler,mtsource] Implementing EvenSpread HA support across nodes within a zone #593

Open
aavarghese opened this issue May 4, 2021 · 8 comments · Fixed by #768
Open

[scheduler,mtsource] Implementing EvenSpread HA support across nodes within a zone #593

aavarghese opened this issue May 4, 2021 · 8 comments · Fixed by #768
Assignees
@aavarghese
Labels
kind/feature-request triage/accepted Issues which should be fixed (post-triage)

Comments

@aavarghese
Copy link
Contributor

Problem
Implementing HA across pods within a zone (# of pods is not static unlike # of zones, so spreading equally may also mean rebalancing)

More info in #587, #463

Persona:
Which persona is this feature for?

Exit Criteria
Vreplicas are evenly spread across pods in each zone (check kafkasource status placement field)

Time Estimate (optional):
How many developer-days do you think this may take to resolve?

Additional context (optional)
Add any other context about the feature request here.
@aavarghese aavarghese mentioned this issue May 4, 2021
Merged
@aavarghese
Copy link
Contributor Author

/assign

@aavarghese
Copy link
Contributor Author

@lionelvillard I think we meant "across nodes within a zone" and not "pods" right?

@lionelvillard
Copy link
Contributor

yes

@aavarghese aavarghese changed the title [scheduler,mtsource] Implementing HA support across pods within a zone (EvenSpread) [scheduler,mtsource] Implementing EvenSpread HA support across nodes within a zone Jun 11, 2021
@aavarghese aavarghese mentioned this issue Jun 14, 2021
Closed
@aavarghese aavarghese mentioned this issue Jul 15, 2021
Merged
@aavarghese
Copy link
Contributor Author

/reopen

@knative-prow-robot
Copy link
Contributor

@aavarghese: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@aavarghese
Copy link
Contributor Author

#768 (comment)

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 21, 2021
@pierDipi
Copy link
Member

/remove-lifecycle stale
/triage accepted

@knative-prow-robot knative-prow-robot added triage/accepted Issues which should be fixed (post-triage) and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 20, 2022
@pierDipi pierDipi reopened this Jan 20, 2022
matzew added a commit to matzew/eventing-kafka that referenced this issue Apr 20, 2022
@openshift-cherrypick-robot @matzew
Just run the channel tests.... (knative-extensions#593)
472b0e7 
Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>

Co-authored-by: Matthias Wessendorf <mwessend@redhat.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@aavarghese aavarghese

Labels
kind/feature-request triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Milestone
No milestone
4 participants
@aavarghese @lionelvillard @pierDipi @knative-prow-robot