[SERVER-43819] Standardize logging of index builds between index types and between index builds on primaries vs secondaries Created: 03/Oct/19  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Diagnostics, Index Maintenance, Logging
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Maria van Keulen Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Storage Execution
Participants:
Linked BF Score: 13

 Description   

Presently, we are inconsistent with logging index builds. For example, _id indexes do not log "starting index build" like other indexes do unless they belong to specific collections that use that code path.
Additionally, in some cases it is not sufficient to rely on logs in low-level IndexBuildBlock code to determine index build progress. We have logs on the primary that are outside of low-level IndexBuildBlock code, e.g., registering the build. However, we do not log the beginning of index builds on secondaries. An index build can fail at a variety of points, in some cases before the pertinent logs occur, so it is useful to have additional progress logs available.

  1. We should standardize logging of index builds between _id indexes and non-_id indexes.
  2. We should ensure that logs exist, possibly at different log levels, early on in index builds on both primaries and secondaries.
  3. We should add more information about the collection on which the index build is occurring in our existing logs.

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