Low Issue Summary
When there is an issue with one or more index mapping in the search server, it logs the following message but doesn't log the corresponding fields/mapping where the error is present -
IndexingSynchronizationService Mapping in the search server is present but not compatible with this version of indexing. Unable to continue, operator intervention is required.
This behaviour is not consistent and sometimes the expected error message is logged.
This is reproducible on Data Center: yes
Steps to Reproduce
- Same as
BSERV-13310 - JDK 9
Expected Results
Following are logged in the logs:
2022-05-09 18:00:44,986 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService The mapping for type 'bitbucke t-search/file' in the search server is invalid. Errors: [Field 'archived' is missing] 2022-05-09 18:00:44,986 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService The mapping for type 'bitbucke t-index-state/indexstate' in the search server is invalid. Errors: [Field 'archived' is missing] 2022-05-09 18:00:44,986 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService The mapping for type 'bitbucke t-repository/repository' in the search server is invalid. Errors: [Field 'archived' is missing] 2022-05-09 18:00:44,986 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService Mapping in the search server i s present but not compatible with this version of indexing. Unable to continue, operator intervention is required.
Actual Results
2022-05-09 18:00:44,986 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService Mapping in the search server i s present but not compatible with this version of indexing. Unable to continue, operator intervention is required.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Missing error logs when mapping is invalid in search server
Issue Summary
When there is an issue with one or more index mapping in the search server, it logs the following message but doesn't log the corresponding fields/mapping where the error is present -
IndexingSynchronizationService Mapping in the search server is present but not compatible with this version of indexing. Unable to continue, operator intervention is required.
This behaviour is not consistent and sometimes the expected error message is logged.
This is reproducible on Data Center: yes
Steps to Reproduce
- Same as
BSERV-13310 - JDK 9
Expected Results
Following are logged in the logs:
2022-05-09 18:00:44,986 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService The mapping for type 'bitbucke t-search/file' in the search server is invalid. Errors: [Field 'archived' is missing] 2022-05-09 18:00:44,986 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService The mapping for type 'bitbucke t-index-state/indexstate' in the search server is invalid. Errors: [Field 'archived' is missing] 2022-05-09 18:00:44,986 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService The mapping for type 'bitbucke t-repository/repository' in the search server is invalid. Errors: [Field 'archived' is missing] 2022-05-09 18:00:44,986 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService Mapping in the search server i s present but not compatible with this version of indexing. Unable to continue, operator intervention is required.
Actual Results
2022-05-09 18:00:44,986 ERROR [Caesium-1-1] c.a.b.i.s.i.IndexingSynchronizationService Mapping in the search server i s present but not compatible with this version of indexing. Unable to continue, operator intervention is required.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
-
Manish
-
- Votes:
-
2 Vote for this issue
- Watchers:
-
6 Start watching this issue
- Created:
- Updated:
- Resolved: