[SERVER-54315] Enable logkeeper v3 by default Created: 04/Feb/21  Updated: 06/Dec/22  Resolved: 07/Feb/22

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Backlog - Evergreen Team (Inactive)
Resolution: Won't Do Votes: 0
Labels: tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-55628 Evergreen.yml lint rule: Enable no-ke... Closed
Gantt Dependency
Problem/Incident
Related
is related to SERVER-59767 Catch signal jasper process errors Closed
Assigned Teams:
Evergreen
Backport Requested:
v5.0
Sprint: Evergreen 2021-05-31, Evergreen 2021-06-14, Evergreen 2021-06-28, Evergreen 2021-07-12, Evergreen 2021-08-23, Evergreen 2021-09-06, Evergreen 2021-09-20, Evergreen 2021-10-04, Evergreen 2021-12-27, Evergreen 2022-01-10
Participants:
Linked BF Score: 148
Story Points: 4

 Description   

Enable logkeeper v3 on all x86 build variants by passing in the Jasper option to resmoke to the build variant definitions in evergreen.yml.

Rollout will be in the following phases with enough gap in between for the affect on Cedar to be observed.

1. Add a single daily builder
2. Add a single required builder
3. Add remaining required builders
4. Add all remaining x86 builders



 Comments   
Comment by April Schoffer [ 07/Feb/22 ]

Closing this given we are closing PM-1439 and will continue to use Logkeeper for resmoke logs until we are able to provide a scalable logging solution via PM-2695.

Comment by Jonathan Brill [ 15/Oct/21 ]

Before we turn this on again we will do more due diligence to make sure cedar can handle the load. The plan is captured in EVG-15615.
We're time-boxing the effort to get the solutions outlined there to 11/25 at which point we will go back and revisit our options.

Comment by Julian Edwards [ 14/Oct/21 ]

Will link all related tickets.

Comment by Brian Samek [ 14/Oct/21 ]

jonathan.brill julian.edwards Could you link a ticket that this is blocked on?

Comment by Githook User [ 06/Oct/21 ]

Author:

{'name': 'julianedwards', 'email': 'julian.edwards@mongodb.com'}

Message: SERVER-54315: turn of jasper resmoke
Branch: master
https://github.com/mongodb/mongo/commit/9b77b2447deea6ffbeba320b89969ece04efe20d

Comment by Jonathan Brill [ 06/Oct/21 ]

We're going to turn this off again because the db is having trouble handling the load.
We'll turn it back on once we've implemented a solution to reduce the pressure on the db.

Comment by Daniel Gottlieb (Inactive) [ 05/Oct/21 ]

For server engineers watching this server ticket, the prior patch turned this on for:

  • ! Shared Library Enterprise RHEL 8.0
  • Enterprise RHEL 8.0

I suspect keeping an eye out for anything unusual on those variants would be appreciated

Comment by Githook User [ 05/Oct/21 ]

Author:

{'name': 'julianedwards', 'email': 'julian.edwards@mongodb.com'}

Message: SERVER-54315: Turn on jasper resmoke for a single required build and a single daily build
Branch: master
https://github.com/mongodb/mongo/commit/cf6da1848adeee1ef16f3ef5f26327669f493120

Comment by Julian Edwards [ 22/Sep/21 ]

Yes, thanks for catching that! Linked EVG-15418.

Comment by Githook User [ 17/Sep/21 ]

Author:

{'name': 'julianedwards', 'email': 'julian.edwards@mongodb.com'}

Message: SERVER-54315: Turn off jasper resmoke
Branch: master
https://github.com/mongodb/mongo/commit/c4339e6e20c2d6cac811fb0d91a7b0ad9390957d

Comment by Githook User [ 01/Sep/21 ]

Author:

{'name': 'julianedwards', 'email': 'julian.edwards@mongodb.com'}

Message: SERVER-54315: Enable jasper resmoke for a single required build
Branch: master
https://github.com/mongodb/mongo/commit/81d666c6c78ef59a66eb3a2c3e9224b65edc4430

Comment by Githook User [ 19/Aug/21 ]

Author:

{'name': 'julianedwards', 'email': 'julian.edwards@mongodb.com'}

Message: SERVER-54315: Enable jasper resmoke for a single daily build
Branch: master
https://github.com/mongodb/mongo/commit/4febdf30b44ddebf5d238721015e5d59db663086

Comment by Iryna Zhuravlova [ 06/Apr/21 ]

brooke.miller Thanks for letting us know. I think it should be fine, we will let STM know if we need any assistance. 

Comment by Brooke Miller [ 06/Apr/21 ]

FYI iryna.zhuravlova we've re-assigned this to Evergreen because julian.edwards has been leading the effort for PM-1439. Let us know if you have any questions or concerns with this move.

Generated at Thu Feb 08 05:33:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.