Missing subspace provider in FDBRecordStore logs #2936
Assignees
Labels
bug
Something isn't working
Comments
alecgrieser
added a commit
to alecgrieser/fdb-record-layer
that referenced
this issue
Oct 4, 2024
…logs There were a handful of places in the `FDBRecordStore` class that were were logging but didn't include the subspace provider as context. This means that we couldn't tell what store the logs were trying to log about, which made it hard to correlate with other operations to the store. This resolves that by adding in the missing information to the missing logs. This fixes FoundationDB#2936.
alecgrieser
added a commit
to alecgrieser/fdb-record-layer
that referenced
this issue
Oct 4, 2024
…logs There were a handful of places in the `FDBRecordStore` class that were were logging but didn't include the subspace provider as context. This means that we couldn't tell what store the logs were trying to log about, which made it hard to correlate with other operations to the store. This resolves that by adding in the missing information to the missing logs. This fixes FoundationDB#2936.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are a couple of places in
FDBRecordStorewhere we're logging information about something that happened in the store, but we're not including the subspace provider so we're missing out on which record store the log is about. For example, the "index state change" message, indicating an index was either enabled or disabled, is missing those log keys.The text was updated successfully, but these errors were encountered: