Problem Note 61846: Elasticsearch might fail with an "IllegalStateException: failed to obtain node locks..." error in SAS® Visual Investigator
 |  |  |  |
When you restart services for SAS Visual Investigator, Elasticsearch might fail to start.
When you encounter this problem, you might see an error similar to the following in the Elasticsearch service log:
[2017-12-15T08:36:08,847][ERROR][o.e.b.Bootstrap ] Exception
java.lang.IllegalStateException: failed to obtain node locks, tried
[[/opt/sas/viya/config/data/svi-elasticsearch/sas-elasticsearch]] with lock id
[0]; maybe these locations are not writable or multiple nodes were started
without increasing [node.max_local_storage_nodes] (was [1])?
java.lang.IllegalStateException: failed to obtain node locks, tried
[[/opt/sas/viya/config/data/svi-elasticsearch/sas-elasticsearch]] with lock id
[0]; maybe these locations are not writable or multiple nodes were started
without increasing [node.max_local_storage_nodes] (was [1])?
If this problem occurs, you might need to end processes by using UNIX commands. The following command lists any Elasticsearch service processes that are still running:
ps wwuax | grep elastic
The Linux kill command also ends the processes. When you have stopped all the Elasticsearch service processes that were still running, restart Elasticsearch.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Visual Investigator | Linux for x64 | 10.3 | Viya | ||
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2018-03-06 16:54:12 |
| Date Created: | 2018-02-15 10:22:04 |