SUPPORT / SAMPLES & SAS NOTES
Problem Note 70864: A full index with a large amount of data might cause a memory error in SAS® Visual Investigator
 |  |  |  |  |
In SAS Visual Investigator, you might run out of memory if you run a full index with a large amount of data using the Postgres database.
The problem occurs with the svi-indexer microservice. Increasing the svi-indexer java maximum heap size does not prevent the condition from occurring.
One or more of the following messages might occur in svi-indexer log:
i. [datetime] WARN 283787 --- [ ThreadsMonitor] o.a.g.i.m.ThreadsMonitoringProcess : service Thread 2710 (0xa96) is stuck
ii. [datetime] WARN 283787 --- [ StatSampler] o.a.g.i.statistics.HostStatSampler : service Statistics sampling thread detected a wakeup delay of 19908 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics.
iii. java.lang.OutOfMemoryError: Java heap space
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Visual Investigator (on SAS Viya 3.x) | Linux for x64 | 10.8 | Viya | ||