This repository was archived by the owner on Jan 28, 2022. It is now read-only.
Add multiple pods with anti affinity #165
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hub.com/stuartleeks/azure-databricks-operator into es/add-multiple-pods-with-anti-affinity
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
EliiseS
requested review from
035 and
Azadehkhojandi
and removed request for
035
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Otherwise load tests wont be able to run in the build pipeline
EliiseS
force-pushed
the
es/add-multiple-pods-with-anti-affinity
branch
from
71afdc5 to
7066776
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to address the issue #164 Operator becomes unavailable if pod restarts.
We've increased the operator pod count to 2 and the pods will be deployed on different nodes to keep the operator operational in case a pod or a node goes down.
We've also tested that this change has no negative effect on the performance of the operator, the results of the test can be seen below:
