This repository has been archived by the owner. It is now read-only.

Reduce default number of compilation VMs to 4 #137

Closed
mrdavidlaing opened this Issue Mar 10, 2013 · 5 comments

Comments

Projects
None yet
4 participants
@mrdavidlaing
Contributor

mrdavidlaing commented Mar 10, 2013

The default number of compilation VMs is 10.

On my AWS account this seems to cause timeout errors (possibly due to AWS API rate throttling?)

Reducing the number of compilation VMs to 4 prevents this from happening.

Proposal - the default is reduced to 4

vcap@ip-10-245-16-20:~$ bosh cf deploy
Current CloudFoundry system is '/var/vcap/store/systems/production'
Deployment set to `/var/vcap/store/systems/production/deployments/production-core.yml'
bosh -n --color deploy
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Compiling deployment manifest...

Director task 3

Preparing deployment
  binding deployment (00:00:00)                                                                     
  binding releases (00:00:00)                                                                       
  binding existing deployment (00:00:00)                                                            
  binding resource pools (00:00:00)                                                                 
  binding stemcells (00:00:00)                                                                      
  binding templates (00:00:00)                                                                      
  binding properties (00:00:00)                                                                     
  binding unallocated VMs (00:00:00)                                                                
  binding instance networks (00:00:00)                                                              
Done                    9/9 00:00:00                                                                

Preparing package compilation
  finding packages to compile (00:00:00)                                                            
Done                    1/1 00:00:00                                                                

Compiling packages
  dea_node08/1: Request limit exceeded. (00:00:29)                                                  
  dea_jvm/3: Request limit exceeded. (00:00:30)                                                     
  dea_ruby18/8: Request limit exceeded. (00:00:30)                                                  
  git/1: Request limit exceeded. (00:00:38)                                                         
  dea_jvm7/1 (00:03:29)                                                                             
  dea_ruby19/7 (00:08:00)                                                                           
  dea_node04/3 (00:08:16)                                                                           
  dea_node06/3 (00:09:05)                                                                           
  redis22/1: Timed out pinging to 84a3ea1b-6c9d-4f1f-b806-03bb03460d9f after 600 seconds (00:10:29) 
  imagemagick/2 (00:19:35)                                                                          
Error                   10/30 00:19:35                                                              

Error 100: Request limit exceeded.

Task 3 error
/usr/local/lib/ruby/1.9.1/rake/file_utils.rb:53:in `block in create_shell_runner': Command failed with status (1): [bosh -n --color deploy...] (RuntimeError)
    from /usr/local/lib/ruby/1.9.1/rake/file_utils.rb:45:in `call'
    from /usr/local/lib/ruby/1.9.1/rake/file_utils.rb:45:in `sh'
    from /usr/local/lib/ruby/gems/1.9.1/gems/bosh-cloudfoundry-0.6.1/lib/bosh/cli/commands/cf.rb:632:in `bosh_cmd'
    from /usr/local/lib/ruby/gems/1.9.1/gems/bosh-cloudfoundry-0.6.1/lib/bosh/cli/commands/cf.rb:156:in `block in deploy'
    from /usr/local/lib/ruby/gems/1.9.1/gems/bosh-cloudfoundry-0.6.1/lib/bosh/cli/commands/cf.rb:154:in `each'
    from /usr/local/lib/ruby/gems/1.9.1/gems/bosh-cloudfoundry-0.6.1/lib/bosh/cli/commands/cf.rb:154:in `deploy'
    from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/command_handler.rb:57:in `run'
    from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/runner.rb:61:in `run'
    from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/lib/cli/runner.rb:18:in `run'
    from /usr/local/lib/ruby/gems/1.9.1/gems/bosh_cli-1.0.3/bin/bosh:16:in `<top (required)>'
    from /usr/local/bin/bosh:23:in `load'
    from /usr/local/bin/bosh:23:in `<main>'
@tpradeep

This comment has been minimized.

Contributor

tpradeep commented Mar 13, 2013

Yes mate. I am finding the way to do it. Facing the same problem of hardware limitations

Check this

https://github.com/cloudfoundry/bosh/blob/master/release/jobs/director/spec#L28

@tpradeep

This comment has been minimized.

Contributor

tpradeep commented Mar 13, 2013

Have you tried decreasing workers count in production-core.yml ?

@drnic

This comment has been minimized.

Contributor

drnic commented Mar 13, 2013

I think that's new for 1.5.0 (coming soon). We could try passing the property now for edge users? (and it'll be ignored for older stemcells)

On Wed, Mar 13, 2013 at 6:33 AM, Pradeep Tummala notifications@github.com
wrote:

Have you tried decreasing workers count in production-core.yml ?

Reply to this email directly or view it on GitHub:
#137 (comment)

@anderssv

This comment has been minimized.

Contributor

anderssv commented Mar 18, 2013

On a long shot I also reported an issue with BOSH, it seems to me it really should be handled while running. Maybe with some sort of max tries. cloudfoundry/bosh#81

@drnic

This comment has been minimized.

Contributor

drnic commented Jul 18, 2013

I think this is now fixed upstream in bosh.

@drnic drnic closed this Jul 18, 2013

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.