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

Update to option enable client.QPS and client.Burst #6635

Merged
merged 1 commit into from
Apr 10, 2015

Conversation

timothysc
Copy link
Member

Changes from #6203 & #6207 drastically affect throughput. This change will option enable the kcm for tuning QPS, leave default QPS on kubelets but enable higher traffic to<>from kcm.

@wojtek-t @fgrzadkowski

Also would affect:
#4866

@wojtek-t
Copy link
Member

wojtek-t commented Apr 9, 2015

There is already #6569 in flight.
But I'm fine with your approach if you do the same for scheduler.

@lavalamp
Copy link
Member

lavalamp commented Apr 9, 2015

I'd prefer the name "max_outgoing_qps" and I prefer the approach in #6569. But I think #6569 is running on European time, so you can probably win the race if you want to update this.

I don't think this parameter matters in practice for scheduler (yet), but it's good to have it in everything that's an apiserver client for completeness/consistency.

@wojtek-t
Copy link
Member

wojtek-t commented Apr 9, 2015

@lavalamp This parameter matter for scheduler as well - without any limits scheduler is able to scheduler even up to 15 pod per second, but with the current default limit set to 5 it cannot schedule more than 2-3 pods per second (which I think is below our expectations). So we definitely want to change it for the scheduler too.

@timothysc
Copy link
Member Author

I'll have a roll up shortly including details from #6569

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@lavalamp
Copy link
Member

lavalamp commented Apr 9, 2015

@wojtek-t oh, you're saying the scheduler has a limit right now? I agree it definitely should not be that low. Scheduler doesn't really need a limit IMO, it can't dos apiserver given its current algorithm. So it should be high, like 50 QPS...

@timothysc
Copy link
Member Author

updated per review, I wait for feedback b4 final updates.

@timothysc timothysc changed the title Update to option enable client.QPS on the controller-manager. Update to option enable client.QPS and client.Burst Apr 9, 2015
@@ -66,6 +66,8 @@ func NewSchedulerServer() *SchedulerServer {
func (s *SchedulerServer) AddFlags(fs *pflag.FlagSet) {
fs.IntVar(&s.Port, "port", s.Port, "The port that the scheduler's http service runs on")
fs.Var(&s.Address, "address", "The IP address to serve on (set to 0.0.0.0 for all interfaces)")
s.ClientConfig.QPS=20.0
Copy link
Member

Choose a reason for hiding this comment

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

Suggest letting burst go to 80 or 100

@lavalamp
Copy link
Member

lavalamp commented Apr 9, 2015

Looking good, two minor quibbles

@lavalamp
Copy link
Member

lavalamp commented Apr 9, 2015

Also, gofmt :)

@wojtek-t
Copy link
Member

LGTM (we can tune the limit in the future if necessary).
Since all the comments by @lavalamp are applied, I'm kicking Shippable since it's red now and will merge on green.

@wojtek-t
Copy link
Member

@timothysc Ohh - actually can you please squash commits before I merge it? Thanks

and change default on max_requests_inflight.
@timothysc
Copy link
Member Author

squashed.

@wojtek-t
Copy link
Member

Thanks - will merge on green (we can tune the values in the future).

@timothysc
Copy link
Member Author

+1.

wojtek-t added a commit that referenced this pull request Apr 10, 2015
Update to option enable client.QPS and client.Burst
@wojtek-t wojtek-t merged commit 2e24c50 into kubernetes:master Apr 10, 2015
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.

4 participants