# ES Fails Initializing when Index is on NAS **URL:** \ **Category:** Elasticsearch\ **Created:** [December 5, 2014, 9:41pm UTC](https://discuss.elastic.co/t/es-fails-initializing-when-index-is-on-nas/21116 "2014-12-05T21:41:19Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Yingkai\_Gao\_2](https://avatars.discourse-cdn.com/v4/letter/y/7ea924/32.png) [@Yingkai\_Gao\_2](https://discuss.elastic.co/u/Yingkai_Gao_2)\ **Post date:** [December 5, 2014, 9:41pm UTC](https://discuss.elastic.co/t/es-fails-initializing-when-index-is-on-nas/21116/1 "2014-12-05T21:41:19Z")
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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 6, 2014, 6:38am UTC](https://discuss.elastic.co/t/es-fails-initializing-when-index-is-on-nas/21116/2 "2014-12-06T06:38:03Z")
Start the service, do a ps|grep java and grab the command that is called then run it manually. You may find it returns more info you can use to resolve your issue. Otherwise you can turn up the logging levels in logging.yml. On 6 December 2014 at 08:41, Yingkai Gao [kyle.ygao@gmail.com](mailto:kyle.ygao@gmail.com) wrote: > 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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8sZvXN4L%2BO4pXN9%3DXXO7etgBN2hg4ktFm8VJSW-HafEA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8sZvXN4L%2BO4pXN9%3DXXO7etgBN2hg4ktFm8VJSW-HafEA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Yingkai\_Gao\_2](https://avatars.discourse-cdn.com/v4/letter/y/7ea924/32.png) [@Yingkai\_Gao\_2](https://discuss.elastic.co/u/Yingkai_Gao_2)\ **Post date:** [December 6, 2014, 3:27pm UTC](https://discuss.elastic.co/t/es-fails-initializing-when-index-is-on-nas/21116/3 "2014-12-06T15:27:21Z")
I set the logger level to TRACE and get the following loggings. It seems ES failed obtaining the node lock. But I still have no idea how to solve it. [2014-12-06 10:22:00,101][INFO][node] [kyle] version[1.4.0], pid[18889], build[bc94bd8/2014-11-05T14:26:12Z] [2014-12-06 10:22:00,102][INFO][node] [kyle] initializing ... [2014-12-06 10:22:00,103][DEBUG][node] [kyle] using home [/bos/usr0/yingkaig/downloads/elasticsearch-debug], config [/bos/usr0/yingkaig/downloads/elasticsearch-debug/config], data [[/bos/tmp11/yingkaig/index.debug]], logs [/bos/usr0/yingkaig/temp/logs], work [/bos/usr0/yingkaig/downloads/elasticsearch-debug/work], plugins [/bos/usr0/yingkaig/downloads/elasticsearch-debug/plugins] [2014-12-06 10:22:00,111][DEBUG][plugins] [kyle] [/bos/usr0/yingkaig/downloads/elasticsearch-debug/plugins] directory does not exist. [2014-12-06 10:22:00,112][INFO][plugins] [kyle] loaded , sites [2014-12-06 10:22:00,152][DEBUG][common.compress.lzf] using encoder [VanillaChunkDecoder] and decoder[{}] [2014-12-06 10:22:00,157][TRACE][env] [kyle] obtaining node lock on /bos/tmp11/yingkaig/index.debug/debug/nodes/0 ... On Saturday, December 6, 2014 1:38:38 AM UTC-5, Mark Walkom wrote: > Start the service, do a ps|grep java and grab the command that is called > then run it manually. > You may find it returns more info you can use to resolve your issue. > > Otherwise you can turn up the logging levels in logging.yml. > > On 6 December 2014 at 08:41, Yingkai Gao \<[kyle...@gmail.com](mailto:kyle...@gmail.com) \\> > wrote: > > > 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](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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/47a5a4d1-7bf9-4e89-ba95-1fd206d5da87%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/47a5a4d1-7bf9-4e89-ba95-1fd206d5da87%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Yingkai\_Gao\_2](https://avatars.discourse-cdn.com/v4/letter/y/7ea924/32.png) [@Yingkai\_Gao\_2](https://discuss.elastic.co/u/Yingkai_Gao_2)\ **Post date:** [December 7, 2014, 1:13am UTC](https://discuss.elastic.co/t/es-fails-initializing-when-index-is-on-nas/21116/4 "2014-12-07T01:13:10Z")
Okay. I've got a super weird solution to this problem and I really think it does not make any sense. After running jstack with the pid of ES, I found that the java process blocked at a native method lock0 as the following stack log shows. "main" #1 prio=5 os\_prio=0 tid=0x000000000238f000 nid=0x63ef runnable [0x000000004110e000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.FileDispatcherImpl.lock0(Native Method) at sun.nio.ch.FileDispatcherImpl.lock(FileDispatcherImpl.java:90) at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1067) at java.nio.channels.FileChannel.tryLock(FileChannel.java:1155) at org.apache.lucene.store.NativeFSLock.obtain(NativeFSLockFactory.java:169) - locked \<0x00000000c10e2898\> (a org.apache.lucene.store.NativeFSLock) at org.elasticsearch.env.NodeEnvironment.(NodeEnvironment.java:83) at org.elasticsearch.node.internal.InternalNode.(InternalNode.java:157) at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:159) at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:70) at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:203) at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:32) Then I just ran pstack with the pid. While I got nothing usefully, the blocked process magically continued and successfully obtained the file lock and recovered index. I believe cause of the problem is that the configuration of file locking on the NAS/NFS is inappropriate. Because I don't have the privilege to re-configure it, I'm just going to use this solution but still need some explanation... On Friday, December 5, 2014 4:41:19 PM UTC-5, Yingkai Gao wrote: > 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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/cb26e818-a0fa-44e3-8552-2532a951829e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cb26e818-a0fa-44e3-8552-2532a951829e%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 7, 2014, 8:38am UTC](https://discuss.elastic.co/t/es-fails-initializing-when-index-is-on-nas/21116/5 "2014-12-07T08:38:08Z")
Does ES have permissions to the mount. On 7 December 2014 at 12:13, Yingkai Gao [kyle.ygao@gmail.com](mailto:kyle.ygao@gmail.com) wrote: > Okay. I've got a super weird solution to this problem and I really think > it does not make any sense. > After running jstack with the pid of ES, I found that the java process > blocked at a native method lock0 as the following stack log shows. > "main" #1 prio=5 os\_prio=0 tid=0x000000000238f000 nid=0x63ef runnable > [0x000000004110e000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.FileDispatcherImpl.lock0(Native Method) > at sun.nio.ch.FileDispatcherImpl.lock(FileDispatcherImpl.java:90) > at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1067) > at java.nio.channels.FileChannel.tryLock(FileChannel.java:1155) > at > org.apache.lucene.store.NativeFSLock.obtain(NativeFSLockFactory.java:169) > > - locked \<0x00000000c10e2898\> (a org.apache.lucene.store.NativeFSLock) > at org.elasticsearch.env.NodeEnvironment.(NodeEnvironment.java:83) > at > org.elasticsearch.node.internal.InternalNode.(InternalNode.java:157) > at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:159) > at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:70) > at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:203) > at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:32) > > Then I just ran pstack with the pid. While I got nothing usefully, the > blocked process magically continued and successfully obtained the file lock > and recovered index. > I believe cause of the problem is that the configuration of file locking > on the NAS/NFS is inappropriate. Because I don't have the privilege to > re-configure it, I'm just going to use this solution but still need some > explanation... > > On Friday, December 5, 2014 4:41:19 PM UTC-5, Yingkai Gao wrote: > > > 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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/cb26e818-a0fa-44e3-8552-2532a951829e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cb26e818-a0fa-44e3-8552-2532a951829e%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/cb26e818-a0fa-44e3-8552-2532a951829e%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/cb26e818-a0fa-44e3-8552-2532a951829e%40googlegroups.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9XUmoe%2BYtLA%2Bf00qFzfQuKBWu1BoR3bL3AXY5pJd56aA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9XUmoe%2BYtLA%2Bf00qFzfQuKBWu1BoR3bL3AXY5pJd56aA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [December 7, 2014, 5:11pm UTC](https://discuss.elastic.co/t/es-fails-initializing-when-index-is-on-nas/21116/6 "2014-12-07T17:11:22Z")
Your NAS does not work as long as it does not support file locking. Remote file locks were never supported on NAS/NFS and that is the reason why many programs can not run on NAS/NFS. Jörg On 12/7/14, Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com) wrote: > Does ES have permissions to the mount. > > On 7 December 2014 at 12:13, Yingkai Gao [kyle.ygao@gmail.com](mailto:kyle.ygao@gmail.com) wrote: > > > Okay. I've got a super weird solution to this problem and I really think > > it does not make any sense. > > After running jstack with the pid of ES, I found that the java process > > blocked at a native method lock0 as the following stack log shows. > > "main" #1 prio=5 os\_prio=0 tid=0x000000000238f000 nid=0x63ef runnable > > [0x000000004110e000] > > java.lang.Thread.State: RUNNABLE > > at sun.nio.ch.FileDispatcherImpl.lock0(Native Method) > > at sun.nio.ch.FileDispatcherImpl.lock(FileDispatcherImpl.java:90) > > at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1067) > > at java.nio.channels.FileChannel.tryLock(FileChannel.java:1155) > > at > > org.apache.lucene.store.NativeFSLock.obtain(NativeFSLockFactory.java:169) > > > > - locked \<0x00000000c10e2898\> (a org.apache.lucene.store.NativeFSLock) > > at org.elasticsearch.env.NodeEnvironment.(NodeEnvironment.java:83) > > at > > org.elasticsearch.node.internal.InternalNode.(InternalNode.java:157) > > at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:159) > > at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:70) > > at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:203) > > at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:32) > > > > Then I just ran pstack with the pid. While I got nothing usefully, the > > blocked process magically continued and successfully obtained the file > > lock > > and recovered index. > > I believe cause of the problem is that the configuration of file locking > > on the NAS/NFS is inappropriate. Because I don't have the privilege to > > re-configure it, I'm just going to use this solution but still need some > > explanation... > > > > On Friday, December 5, 2014 4:41:19 PM UTC-5, Yingkai Gao wrote: > > > > > 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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/cb26e818-a0fa-44e3-8552-2532a951829e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cb26e818-a0fa-44e3-8552-2532a951829e%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/cb26e818-a0fa-44e3-8552-2532a951829e%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/cb26e818-a0fa-44e3-8552-2532a951829e%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9XUmoe%2BYtLA%2Bf00qFzfQuKBWu1BoR3bL3AXY5pJd56aA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9XUmoe%2BYtLA%2Bf00qFzfQuKBWu1BoR3bL3AXY5pJd56aA%40mail.gmail.com). > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGD%3DpoYU2CAbMWpEp4RH54bgWZB8tG31JVodwfw96nQ4Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGD%3DpoYU2CAbMWpEp4RH54bgWZB8tG31JVodwfw96nQ4Q%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:45am UTC](https://discuss.elastic.co/t/es-fails-initializing-when-index-is-on-nas/21116/7 "2017-07-06T00:45:11Z")