Skip to content
New issue

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

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

Already on GitHub? # to your account

MGDSTRM-10039 elevating the priority of broker and zookeeper pods #829

Merged
merged 2 commits into from
Nov 8, 2022

Conversation

shawkins
Copy link
Contributor

@shawkins shawkins commented Nov 3, 2022

also adding some trivial instance profiler changes.

- the direct install method however no longer works due to new
references to classes not in this bundle
@github-actions github-actions bot added operator changes related to operator perf changes related to perf labels Nov 3, 2022
@shawkins shawkins requested review from rareddy and MikeEdgar November 3, 2022 12:15
@shawkins
Copy link
Contributor Author

shawkins commented Nov 3, 2022

I'm not sure what a good naming convention is here. We already have kas-fleetshard-high. I went with core, but you could also go with standard, moderate, medium high, etc.

The choice of 10 for the priority value is also arbitrary. We can of course space that out more if desired - high is 1000000

Copy link
Contributor

@MikeEdgar MikeEdgar left a comment

Choose a reason for hiding this comment

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

lgtm. I'm not sure about the naming either. I don't object to using core. Maybe something like operand-high or similar would be more descriptive?

@rareddy
Copy link
Contributor

rareddy commented Nov 3, 2022

Since "high" name already set precedent, I like the @shawkins idea of going with "standard, moderate, medium high, etc." then there is no ambiguity when referred in conjunction with other class types.


Kafka kafka = kafkaCluster.kafkaFrom(managedKafka, null);

assertEquals("kas-fleetshard-core", kafka.getSpec().getKafka().getTemplate().getPod().getPriorityClassName());
Copy link
Contributor

Choose a reason for hiding this comment

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

I guess these need to be updated to new name to fix the unit tests

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, sorry things were incomplete. Should be good now.

also slightly reducing the broker request to make evictions less common
Copy link
Contributor

@rareddy rareddy left a comment

Choose a reason for hiding this comment

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

lgtm

@MikeEdgar MikeEdgar added this to the 0.31.0 milestone Nov 7, 2022
@sonarqubecloud
Copy link

sonarqubecloud bot commented Nov 7, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@shawkins shawkins merged commit f71bc9f into bf2fc6cc711aee1a0c2a:main Nov 8, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
operator changes related to operator perf changes related to perf
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants