| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Uses Rails transactional tests instead of DatabaseCleaner
transaction strategy because that doesn't work with JS tests
|
|\
| |
| |
| |
| |
| |
| | |
Enable puma by default in GDK
Closes gitlab-development-kit#490
See merge request gitlab-org/gitlab-ce!30285
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Two changes:
1. Move bin/web to bin/web_unicorn(removed PUMA switching logic)
Introduce new shadow script bin/web. Now we have 3 scripts working
together: bin/web, bin/web_puma, bin/web_unicorn
In bin/web, it checks ENV['USE_WEB_SERVER']:
- if value is 'puma' or value is not set, call bin/web_puma
- if value is 'unicorn', call bin/web_unicorn
- report error if other values given
2. Gitlab rails allow ENV setting to override timeout
- ENV['GITLAB_RAILS_RACK_TIMEOUT'] for service_timeout
- ENV['GITLAB_RAILS_WAIT_TIMEOUT'] for wait_timeout
|
| |
| |
| |
| |
| |
| | |
Suggests to use a JSON structured log instead
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
|
| |
| |
| |
| |
| | |
This copies over EE-specific changes to shared configuration files in
CE.
|
|\ \
| | |
| | |
| | |
| | | |
CE-EE parity for config/initializers
See merge request gitlab-org/gitlab-ce!30484
|
| | | |
|
| | |
| | |
| | |
| | | |
We use the `Gitlab.ee` and `.ee?` methods in several initializers now.
|
| | | |
|
| |/
| |
| |
| |
| | |
These files are only used by EE, and are now wrapped in `Gitlab.ee`
blocks for file parity.
|
|/
|
|
|
|
|
|
| |
rack.attack.match_discriminator is only return on
throttle_authenticated_api or throttle_authenticated_web requests, so
we're avoiding logging user_id on blacklist requests
Follow up of https://gitlab.com/gitlab-org/gitlab-ce/issues/62756
|
|
|
|
|
|
| |
Current code uses module attribute which stores value
global instead of locally (thread locally). This results
in concurrent accesses to overwrite the each other values
|
|
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
'63869-store-prometheus-metrics-in-separate-dirs-in-test-and-prod' into 'master'
Use separate Prometheus metrics dirs in dev/test
Closes #63869
See merge request gitlab-org/gitlab-ce!30253
|
| |
| |
| |
| |
| | |
Store Sidekiq and Web server metrics from Prometheus in separate
directories in `development` and `test` environments.
|
| |
| |
| |
| |
| |
| | |
Fetches user based on the value of 'rack.attack.match_discriminator'
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/62756
|
|/
|
|
|
| |
Using `on_master_start` assures that the sampler is started in
master process and not in worker processes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add two new ActiveRecord models:
- RootNamespaceStoragestatistics will persist root namespace statistics
- NamespaceAggregationSchedule will save information when a new update
to the namespace statistics needs to be scheduled
- Inject into UpdateProjectStatistics concern a new callback that will
call an async job to insert a new row onto NamespaceAggregationSchedule
table
- When a new row is inserted a new job is scheduled. This job will
update call an specific service to update the statistics and after that
it will delete thee aggregated scheduled row
- The RefresherServices makes heavy use of arel to build composable
queries to update Namespace::RootStorageStatistics attributes.
- Add an extra worker to traverse pending rows on
NAmespace::AggregationSchedule table and schedule a worker for each one
of this rows.
- Add an extra worker to traverse pending rows on
NAmespace::AggregationSchedule table and schedule a worker for each one
of this rows
|
|
|
|
|
|
|
|
|
|
|
|
| |
Loading `ApplicationSetting` from Redis was responsible for at least 50%
of the CPU load of the Redis cluster on GitLab.com. Since these values
generally don't change very much, we can load this from the database and
cache it in memory, skipping Redis altogther. We use
`ActiveSupport::Cache::MemoryStore` as a drop-in replacement for
`RedisCacheStore` even though we probably don't need synchronized access
within `Thread.current`.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63977
|
|
|
|
|
|
|
|
|
|
| |
We want to call master_restart callback on start too - this callback
is used for cleaning up prometheus files. It has been added to
Omnibus already:
https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3350
So make sure that Unicorn example configs are up-to-date and that
the same callback is called for Puma too.
|
|\
| |
| |
| |
| | |
Remove ignored circuit_breaker columns
See merge request gitlab-org/gitlab-ce!30159
|
| |
| |
| |
| |
| |
| | |
The circuit breaker itself got removed a while ago, when that happened
some parts got left behind. Using grep old stale settings and
validations were found and are now removed.
|
|\ \
| | |
| | |
| | |
| | | |
Copy Settings initializer from EE
See merge request gitlab-org/gitlab-ce!30140
|
| | | |
|
| |/
| |
| |
| | |
This brings parity between the two versions.
|
|\ \
| | |
| | |
| | |
| | | |
Monitor database transaction activity for Rails
See merge request gitlab-org/gitlab-ce!29928
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently we don't have good insight into the affect of Rails
transaction blocks on the application. If these blocks are held open for
extended periods, they can have detrimental effects on the application.
This change will allow us to track these transactions, with the aim
of reducing their duration.
|
| |/
|/|
| |
| |
| |
| | |
https://community.atlassian.com/t5/Jira-questions/Is-it-quot-JIRA-quot-or-quot-Jira-quot/qaq-p/681163
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
|\ \
| | |
| | |
| | |
| | | |
Remove Sentry settings from application settings
See merge request gitlab-org/gitlab-ce!28447
|
| | | |
|
|/ / |
|
|/ |
|
|
|
|
|
|
|
| |
This is a small change to move AfterCommitQueue.inside_transaction?
to Gitlab::Database.inside_transaction? Since this change is required
by different changes which may not arrive in sequence, it's easier
to extract this change out on it's own.
|
|
|
|
|
|
|
|
| |
Add index for pages domain ssl auto renewal
Add PagesDomain.needs_ssl_renewal scope
Add cron worker for ssl renewal
Add worker for ssl renewal
Add pages ssl renewal worker queues settings
|
|\
| |
| |
| |
| | |
Backport changes made by EE to various YAML configuration files
See merge request gitlab-org/gitlab-ce!29606
|
| |
| |
| |
| |
| |
| |
| |
| | |
To make this happen, we need to conditionally add the group_saml
strategy when running tests, but only on EE. This requires some changes
to Gitlab.ee? so that it can be used before/without loading the Rails
environment. We also have to change how we require a few files, so this
can run outside of Rails.
|
|/
|
|
| |
MySQL support has been removed
|
| |
|
|
|
|
|
| |
Because there will be similar observer for PumaWorkerKiller,
it makes sense to keep both on better place.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Gitlab::HTTP now resolves the hostname only once, verifies the IP is not
blocked, and then uses the same IP to perform the actual request, while
passing the original hostname in the `Host` header and SSL SNI field.
|
| |
| |
| |
| |
| |
| |
| | |
It assures that requests are aborted after 60 seconds, otherwise
an exception is raised. This exception is logged by Sentry, also
there is a Prometheus counter for measuring number of requests in each
state.
|
|/
|
|
|
| |
This sampler gathers Puma-specific metrics which can be used by
Prometheus then.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Storing this key in secrets.yml was a bad idea,
it would require users using HA setups to manually
replicate secrets across nodes during update,
it also needed support from omnibus package
* Revert "Generate Let's Encrypt private key"
This reverts commit 444959bfa0b79e827a2a1a7a314acac19390f976.
* Add Let's Encrypt private key to settings
as encrypted attribute
* Generate Let's Encrypt private key
in database migration
|
|
|
|
|
|
|
|
| |
Creates a new filename to register auth logs.
This change should allow SRE's queries to make better queries
through logging infrastructure.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54528
|
|
|
|
| |
Signed-off-by: Utkarsh Gupta <guptautkarsh2102@gmail.com>
|
| |
|
|\
| |
| |
| |
| | |
Add EE fixtures to SeedFu fixture paths
See merge request gitlab-org/gitlab-ce!28241
|
| |
| |
| |
| | |
Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>
|