summaryrefslogtreecommitdiff
path: root/spec/lib/gitlab/sidekiq_middleware
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@13-1-stable-eeGitLab Bot2020-06-185-43/+223
|
* Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot2020-05-202-7/+47
|
* Add latest changes from gitlab-org/gitlab@12-10-stable-eeGitLab Bot2020-04-202-22/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-04-142-44/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-04-022-2/+16
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-261-0/+10
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-232-1/+33
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-171-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-122-6/+6
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-101-0/+11
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-092-0/+66
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-022-22/+29
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-275-0/+264
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-052-0/+166
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-042-166/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-042-0/+166
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-311-0/+45
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-241-0/+72
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-231-4/+11
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-162-2/+115
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-032-84/+0
|
* Add latest changes from gitlab-org/gitlab@masterogolowinski-master-patch-80898GitLab Bot2019-12-161-1/+3
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-221-78/+173
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-051-59/+33
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-041-33/+59
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-281-34/+49
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-231-4/+16
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-231-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-221-17/+29
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-181-0/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-101-0/+13
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-181-1/+1
|
* Change Sidekiq monitor namespaceQingyu Zhao2019-09-111-3/+3
| | | | | | | Move Gitlab::SidekiqMonitor to namespace Gitlab::SidekiqDaemon::Monitor - Class name and file name change - File path change to lib/gitlab/sidekiq_daemon/monitor.rb - Update class usage/reference in other files, including documentation
* Fix for histogram corruption in SidekiqAndrew Newdigate2019-08-301-1/+1
| | | | | | | This fixes a bug in which sidekiq histograms contain invalid labels. See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/7729 for more details.
* Add frozen_string_literal to lib part 2Thong Kuah2019-08-231-0/+2
| | | | | Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
* Put cancelled job in DeadSetsidekiq-interrupt-running-jobs-deadsetKamil Trzciński2019-08-211-1/+9
| | | | | This replicates Sidekiq behavior of pushing dead job into DeadSet.
* Properly handle `sidekiq` skipsidekiq-interrupt-running-jobsKamil Trzciński2019-08-211-0/+12
| | | | Transform `CancelledError` into `JobRetry::Skip`
* Rework `Sidekiq::JobsThreads` into `Monitor`Kamil Trzciński2019-08-212-83/+29
| | | | | | | | | | This makes: - very shallow `Middleware::Monitor` to only request tracking of sidekiq jobs, - `SidekiqStatus::Monitor` to be responsible to maintain persistent connection to receive messages, - `SidekiqStatus::Monitor` to always use structured logging and instance variables
* Allow to interrupt running jobsKamil Trzciński2019-08-211-0/+83
| | | | | | | | | | | | | | | | | This adds a middleware to track all threads for running jobs. This makes sidekiq to watch for redis-delivered notifications. This makes be able to send notification to interrupt running sidekiq jobs. This does not take into account any native code, as `Thread.raise` generates exception once the control gets back to Ruby. The separate measure should be taken to interrupt gRPC, shellouts, or anything else that escapes Ruby.
* Allow measurement for Sidekiq jobs taking > 2.5sAndrew Newdigate2019-08-201-1/+1
| | | | Fix for https://gitlab.com/gitlab-org/gitlab-ce/issues/66319.
* Fix sidekiq memory killer warning messagefix-sidekiq-memory-killer-warn-messageShinya Maeda2019-07-301-2/+5
|
* Adds direct monitoring for sidekiq metricsRyan Cobb2019-07-291-0/+57
| | | | | This adds diirect monitoring for sidekiq metrics. This is done via sidekiq middleware and a sampler to pull from sidekiqs api.
* Logging sidekiq worker class name in SidekiqMemoryKillerprint-sidekiq-class-name-in-memory-killerShinya Maeda2019-07-251-0/+3
| | | | | Currently, SidekiqMemoryKiller does not feed worker class name in the json structured logging. This commit extends the json parameter.
* Migrate correlation and tracing code to LabKitan-use-labkitAndrew Newdigate2019-04-182-2/+2
| | | | | | | | | | | | | | | This change is a fairly straightforward refactor to extract the tracing and correlation-id code from the gitlab rails codebase into the new LabKit-Ruby project. The corresponding import into LabKit-Ruby was in https://gitlab.com/gitlab-org/labkit-ruby/merge_requests/1 The code itself remains very similar for now. Extracting it allows us to reuse it in other projects, such as Gitaly-Ruby. This will give us the advantages of correlation-ids and distributed tracing in that project too.
* Fix the last-ditch memory killer pgroup SIGKILLNick Thomas2019-03-091-1/+1
|
* sidekiq: terminate child processes at shutdownNick Thomas2019-03-041-1/+12
| | | | | | | | | | | | | | | | | | Sidekiq jobs frequently spawn long-lived child processes to do work. In some circumstances, these can be reparented to init when sidekiq is terminated, leading to duplication of work and strange concurrency problems. This commit changes sidekiq so that, if run as a process group leader, it will forward `INT` and `TERM` signals to the whole process group. If the memory killer is active, it will also use the process group when resorting to `kill -9` to shut down. These changes mean that a naive `kill <pid-of-sidekiq>` will now do the right thing, killing any child processes spawned by sidekiq, as long as the process supervisor placed it in its own process group. If sidekiq isn't a process group leader, this new code is skipped.
* SIGSTP should be SIGTSTPNick Thomas2019-03-011-1/+1
|
* Revert "Restart Unicorn and Sidekiq when GRPC throws 14:Endpoint read failed"Nick Thomas2019-02-282-88/+63
| | | | This reverts commit 006753110a462e62f549cdf3c410e73eed068dbf.
* Revert "Prefer to use correlation-id in logs"Kamil Trzciński2018-12-062-2/+2
| | | | This reverts commit 3560b11922fd180eea5cafd0e763e0e601c5c4ee.
* Prefer to use correlation-id in logsKamil Trzciński2018-12-062-2/+2
| | | | This changes `correlation_id` to be `correlation-id` when passed via jobs
View Lorry Controller Status