-
-
Notifications
You must be signed in to change notification settings - Fork 0
chore: Add 35.0.1, remove 33.0.0 #786
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
base: main
Are you sure you want to change the base?
Conversation
Since Druid 35.0.1 the router container failed to start up due to the following error: 'Insufficient configured threads'. The CPU resources are now bumped to be in line with other containers, like the historical and broker containers.
| min: Some(Quantity("300m".to_owned())), | ||
| max: Some(Quantity("1200m".to_owned())), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sad we need this :/
Can you please update the docs in https://docs.stackable.tech/home/nightly/druid/usage-guide/resources-and-storage/?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, will do asap.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 93de48b.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think of this?
// This is calculated using the following formula:
// HDFS resources from hdfs-operator docs + Zookeeper resources from zookeeper-operator docs
// + 2 * (100m + 300m + 300m + 300m + 100m)
AFAIK the operator resources are not included here
Part of stackabletech/docker-images#1371.
This PR updates tests, docs, and getting-started script to Druid 35.0.1