I'm using ElasticSearch-1.4.0 on CentOS-5.6. It works well if I set the index path.data on local/NFS. However, if I set the path.data on a NAS folder, the node keep stuck after initializing and plugins loading.
It looks like this link <http://elasticsearch-users.115913.n3.nabble.com/ElasticSearch-fails-on-NFS-makes-tons-of-empty-directories-in-nodes-td3765236.html> a lot, but I'm using NAS. The node did create the index directories on the NAS path, but it just stopped there. The starting log of ElasticSearch is: [2014-12-05 16:36:12,745][INFO ][node ] [kyle] version[1.4.0], pid[4819], build[bc94bd8/2014-11-05T14:26:12Z] [2014-12-05 16:36:12,747][INFO ][node ] [kyle] initializing ... [2014-12-05 16:36:12,755][INFO ][plugins ] [kyle] loaded [], sites [] Using command df, the file system information of the mounted NAS is: nas-2-25:/exports/volume02 Anyone has any idea how to fix this problem. I know it is not suggested to use NAS for index, but I have to because the infrastructure problem of our cluster. Thanks, Kyle -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
