We are migrating from an old elasticsearch version (1.4) to the latest (2.3.2). We are doing some tests and I'm having some problems.
Our deployment is a bit unconventional, we have several indexes, each one using a different mount point (when we create a new index we also create a mount point with the same name in the data folder, so that ES can store the data in there). The mount points are local to the server, not remote storage.
This works quite well in ES 1.4, but in the latest version we have issues when we try to delete an index. When we send the delete call to elasticsearch the index folder is still mounted, so it cannot be deleted (you get a resource busy error). In the old version it didn't print any errors, it just deleted the contents, leaving the folder, and continued.
With the latest we get several exceptions:
java.nio.file.FileSystemException: Device or resource busy (which was expected)
LockObtainFailedException[Can't lock shard [index-1], timed out after 5000ms];
After this the cluster goes into a Red state and everything stops working.
I there anything we can do to solve this? Maybe an older version that keeps the old behaviour?