[SERVER-71435] Increse verbosity level for range-deleter in resmoke Created: 17/Nov/22  Updated: 29/Oct/23  Resolved: 17/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.4, 6.2.0-rc2, 6.3.0-rc0

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
is duplicated by SERVER-71401 Increase range deleter log verbosity ... Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.2, v6.0, v5.0, v4.4
Sprint: Sharding EMEA 2022-11-28
Participants:
Linked BF Score: 5

 Description   

Resmoke is currently setting at level 2 the log verbosity for the migration component. Considering that the range-deleter component is tightly related with it and emits info useful to better debug migration-related issues, we must increase the verbosity level of such component as well.



 Comments   
Comment by Githook User [ 21/Nov/22 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-71435 Increse verbosity level for range-deleter in resmoke
Branch: v6.0
https://github.com/mongodb/mongo/commit/df0069fbb15c2f56f17e969aedb3ef057100f8c3

Comment by Githook User [ 21/Nov/22 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-71435 Increse verbosity level for range-deleter in resmoke
Branch: v6.2
https://github.com/mongodb/mongo/commit/abcdf5a80b7239938e22fb9a464a58b6c30ef42c

Comment by Githook User [ 17/Nov/22 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-71435 Increse verbosity level for range-deleter in resmoke
Branch: master
https://github.com/mongodb/mongo/commit/1ce4ee1e38f9afe49ffb2e2642a9f46d0432263d

Generated at Thu Feb 08 06:19:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.