SUPPORT / SAMPLES & SAS NOTES
Problem Note 70044: You might encounter intermittent issues when performing indexing during a SAS® Anti-Money Laundering deployment
 |  |  |  |  |
You might encounter the following error intermittently when performing reindexing, either during part of the metadata reconstruction when performing an upgrade-in-place of SAS Anti-Money Laundering or during any reindexing:
An example of the error that you might encounter in the sas-svi-indexer.log file is shown below:
2023-04-20 10:15:39.029 ERROR 14 --- [ctTypeExecutor8] o.s.batch.core.step.AbstractStep : service@@acme [375510ab25804fc2] Encountered an error executing step prepareLinkType in job objectTypeChildJob com.sas.fcs.datahub.DataHubException: The indexed relationships of the type "alert_alertedObject" could not be deleted.
at com.sas.fcs.datahub.services.data.index.IndexService.deleteRelationshipTypeFromIndexIfExist(IndexService.java:625)
at com.sas.fcs.datahub.services.data.index.IndexService.deleteRelationshipTypeFromIndexIfExist(IndexService.java:506)
at com.sas.fcs.datahub.services.data.loader.jobs.scalable.config.infrastructure.objecttype.IndexManagementConfiguration.prepareIndexForRegularLinkLoad(IndexManagementConfiguration.java:873)
at com.sas.fcs.datahub.services.data.loader.jobs.scalable.config.infrastructure.objecttype.IndexManagementConfiguration.lambda$prepareLinkType$16(IndexManagementConfiguration.java:595)
at com.sas.fcs.datahub.services.data.index.IndexService.deleteRelationshipTypeFromIndexIfExist(IndexService.java:625)
at com.sas.fcs.datahub.services.data.index.IndexService.deleteRelationshipTypeFromIndexIfExist(IndexService.java:506)
at com.sas.fcs.datahub.services.data.loader.jobs.scalable.config.infrastructure.objecttype.IndexManagementConfiguration.prepareIndexForRegularLinkLoad(IndexManagementConfiguration.java:873)
at com.sas.fcs.datahub.services.data.loader.jobs.scalable.config.infrastructure.objecttype.IndexManagementConfiguration.lambda$prepareLinkType$16(IndexManagementConfiguration.java:595)
An example of the error that you might encounter in sas-svi-sand-service.log file is shown below:
2023-04-20 10:15:38.922 ERROR 15 --- [nio-8080-exec-1] c.s.s.w.e.GlobalExceptionHandler : sas.svi-indexer@@acme [98c63a539ecb2b35] [dedc2f81-321c-42bd-b0b0-16f2112bece0] Stack trace: com.sas.sand.exception.rest.RestException: Elasticsearch engine response: Code: 400. Error: index_closed_exception:closed. at com.sas.sand.exception.rest.RestExceptionFactory.createRestException(RestExceptionFactory.java:310) at com.sas.sand.web.exception.GlobalExceptionHandler.handleBaseException(GlobalExceptionHandler.java:100) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
This intermittent issue is usually encountered when you are fully reindexing a relationship under the following conditions:
- A relationship (such as relationship A) that does not have a dedicated index and uses the shared index exists.
- Another relationship (such as relationship B) that uses a dedicated index also exists.
- You launch an indexing job that targets relationship that uses shared index (such as relationship A).
- The other relationship that uses a dedicated index (such as relationship B) is undergoing another operation (such as deletion/recreation/...) at the time, which makes that index unavailable.
The workaround is to perform the reindex again.
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Anti-Money Laundering (on SAS 9.x) | Linux for x64 | 8.3 | Viya | ||