puma constantly uses 100% cpu on one core

Created by: ghost

Results to bad gateway some times. Steps to reproduce: Just by running Gitlab service Expected behavior: Leave CPU idle or at most use some percent between tasks? Observed behavior: Constant 100% CPU time on one of the cores (checked by using htop) Relevant logs and/or screen shots: https://plus.google.com/photos/104000320299501254342/albums/5887916224614882801

No other relevant data found in logfiles

Checking Environment ...                                                                                                      

Git configured for git user? ... yes                                                                                          
Has python2? ... yes                                                                                                          
python2 is supported version? ... yes                                                                                         

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.4.0 ? ... OK (1.4.0)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
post-receive hook up-to-date? ... yes
post-receive hooks in repos are links: ... 
Stefanos Kariotidis / server_backups ... ok
Stefanos Kariotidis / Dot Net Utils ... ok
Stefanos Kariotidis / icgrey ... ok
Stefanos Kariotidis / kataxorisi ... ok
Stefanos Kariotidis / kentima ... ok
Stefanos Kariotidis / Python Network Monitor ... ok
Stefanos Kariotidis / spythons ... ok
Stefanos Kariotidis / tkbuilder ... ok
Stefanos Kariotidis / y2mp3 ... ok
Stefanos Kariotidis / flaskboot ... ok
Stefanos Kariotidis / Gitignore ... ok
Stefanos Kariotidis / pyside-2-code ... ok

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes

Checking Sidekiq ... Finished

Checking GitLab ...

Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... no
  Try fixing it:
  Redownload the init script
  For more information see:
  doc/install/installation.md in section "Install Init Script"
  Please fix the error above and rerun the checks.
Projects have satellites? ... 
Stefanos Kariotidis / server_backups ... yes
Stefanos Kariotidis / Dot Net Utils ... yes
Stefanos Kariotidis / icgrey ... yes
Stefanos Kariotidis / kataxorisi ... yes
Stefanos Kariotidis / kentima ... yes
Stefanos Kariotidis / Python Network Monitor ... yes
Stefanos Kariotidis / spythons ... yes
Stefanos Kariotidis / tkbuilder ... yes
Stefanos Kariotidis / y2mp3 ... yes
Stefanos Kariotidis / flaskboot ... yes
Stefanos Kariotidis / Gitignore ... yes
Stefanos Kariotidis / pyside-2-code ... yes
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.8.3)

Checking GitLab ... Finished

Gitlab version: 5.2.0

Setup: Hosted on Ubuntu 12.04.2 64 bit dual core 8GB ram

Created by: hiroponz

Same here. It seems to occur after creating merge request(not always).

By Administrator on 2013-06-11T00:07:01 (imported from GitLab project)

By Administrator on 2013-06-11T00:07:01 (imported from GitLab)

Created by: dzaporozhets

We had same problem few times on one of our servers. Anybody else encountered this issue?

By Administrator on 2013-06-11T08:44:58 (imported from GitLab project)

By Administrator on 2013-06-11T08:44:58 (imported from GitLab)

Created by: mrohnstock

affected us, too. On huge pushes, puma gets locked down (thread lock), until the git push is finish. CPU usage on puma will spread to 100% and gitlab is unusable for this timespan.

By Administrator on 2013-06-11T11:57:20 (imported from GitLab project)

By Administrator on 2013-06-11T11:57:20 (imported from GitLab)

Created by: dzaporozhets

So its because of threads i guess. What if you start puma with workers? https://github.com/gitlabhq/gitlabhq/blob/master/config/puma.rb.example#L94

By Administrator on 2013-06-11T11:57:25 (imported from GitLab project)

By Administrator on 2013-06-11T11:57:25 (imported from GitLab)

Created by: dzaporozhets

@drmonty http pushes right?

By Administrator on 2013-06-11T11:58:19 (imported from GitLab project)

By Administrator on 2013-06-11T11:58:19 (imported from GitLab)

Created by: mrohnstock

@randx right

By Administrator on 2013-06-11T11:58:46 (imported from GitLab project)

By Administrator on 2013-06-11T11:58:46 (imported from GitLab)

Created by: dzaporozhets

Earlier when we had unicorn it stuck only one worker (default setup has 2) so it was not noticed.

By Administrator on 2013-06-11T12:01:57 (imported from GitLab project)

By Administrator on 2013-06-11T12:01:57 (imported from GitLab)

Created by: mrohnstock

I've changed the puma setting, but can't reproduce this issue now (nothing huge to commit so far).

By Administrator on 2013-06-11T12:04:11 (imported from GitLab project)

By Administrator on 2013-06-11T12:04:11 (imported from GitLab)

Created by: dzaporozhets

I guess we should note about amount of workers in installation.md

By Administrator on 2013-06-11T12:04:58 (imported from GitLab project)

By Administrator on 2013-06-11T12:04:58 (imported from GitLab)

Created by: mrohnstock

makes sense

By Administrator on 2013-06-11T12:05:37 (imported from GitLab project)

By Administrator on 2013-06-11T12:05:37 (imported from GitLab)

Created by: dzaporozhets

Added ae90107c

By Administrator on 2013-06-11T12:14:40 (imported from GitLab project)

By Administrator on 2013-06-11T12:14:40 (imported from GitLab)

Created by: Razer6

So I close this one. Report back or reopen if the problem still exits. Hopefully not

By Administrator on 2013-06-28T20:58:07 (imported from GitLab project)

By Administrator on 2013-06-28T20:58:07 (imported from GitLab)