Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Léo-Paul Géneau
gitlab-ce
Commits
d5e073a4
Commit
d5e073a4
authored
May 23, 2018
by
Shinya Maeda
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Revise a comment
parent
c47a434c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
app/workers/rescue_stale_live_trace_worker.rb
app/workers/rescue_stale_live_trace_worker.rb
+3
-3
No files found.
app/workers/rescue_stale_live_trace_worker.rb
View file @
d5e073a4
...
@@ -5,9 +5,9 @@ class RescueStaleLiveTraceWorker
...
@@ -5,9 +5,9 @@ class RescueStaleLiveTraceWorker
def
perform
def
perform
# Reschedule to archive live traces
# Reschedule to archive live traces
#
#
# The target
jobs are
with the following conditions
# The target
s are jobs
with the following conditions
# -
F
inished 1 hour ago, but it has not had an acthived trace yet
# -
It had been f
inished 1 hour ago, but it has not had an acthived trace yet
#
Jobs finished 1 hour ago should have an archived trace. Probably ArchiveTraceWorker failed by Sidekiq's inconsistancy
#
This case happens when sidekiq-jobs of archiving traces are lost in order to restart sidekiq instace which hit RSS limit
Ci
::
BuildTraceChunk
Ci
::
BuildTraceChunk
.
include
(
EachBatch
)
.
include
(
EachBatch
)
.
select
(
:build_id
)
.
select
(
:build_id
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment