Details
-
Bug
-
Resolution: Fixed
-
Critical
-
7.1.4
-
Untriaged
-
0
-
Unknown
Description
The System Event Log provides an important timeline to get a high-level overview of what's occurring on the system. We rely on components using judicious use of this facility.
ERROR level should be reserved for the occasional catastrophic failures
Spamming the system event log results in an unusable artefact.
In the attached set of customer logs, we saw many thousand of the following type of error, meaning we were unable to derive a picture of what had occurred:
2023-07-05T15:49:30.876Z
|
error
|
indexing Index Instance or Partition Error State Change
|
|
{ "definition_id": 15810499631867759000, "error_string": "idx_name_redacted will retry building in the background for reason: Build Already In Progress. Keyspace PROD:_default:redacted.", "group": "DDL", "indexer_id": "d33ecfceaab4295e9c24db93e8ee19e8", "instance_id": 4081695301407191600, "module": "IndexErrorStateChange", "partition_id": 8, "replica_id": 1 }
|
Attachments
Issue Links
- backports to
-
MB-59508 [Backport MB-57723 to 7.2.4] Indexing Service Flooding The System Event Log with 10000 Errors
- Closed