# Zen Discovery, Stop Words and Synonyms Problem **URL:** \ **Category:** Elasticsearch\ **Created:** [November 22, 2012, 4:04pm UTC](https://discuss.elastic.co/t/zen-discovery-stop-words-and-synonyms-problem/9794 "2012-11-22T16:04:13Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Honjoya\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/honjoya_2/32/2576_2.png) [@Honjoya\_2](https://discuss.elastic.co/u/Honjoya_2)\ **Post date:** [November 22, 2012, 4:04pm UTC](https://discuss.elastic.co/t/zen-discovery-stop-words-and-synonyms-problem/9794/1 "2012-11-22T16:04:13Z")
hi I am using ElasticSearch Zen discovery, however I am having trouble in using custom stopword and synonyms. "first server" contains the files put in the second that has the files on the disk. [error] RemoteTransportException [[Punisher] [inet [/ 177.67.118.98:9300]] [indices / create]]; nested: IndexCreationException [[108099] failed to create index]; nested: FailedToResolveConfigException [Failed to resolve path config [/ var / www / html / elasticsearch\_api / current / config / stopwords.txt] tried file path [/ var / www / html / elasticsearch\_api / current / config / stopwords.txt], path file [/ usr / local / share / ElasticSearch / config / var / www / html / elasticsearch\_api / current / config / stopwords.txt], and classpath]; Server 1 - Setup discovery.zen.ping.timeout: 3s discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["192.168.1.102:9200"] Server 2 - setup default. There Any solution? -- ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [November 22, 2012, 4:47pm UTC](https://discuss.elastic.co/t/zen-discovery-stop-words-and-synonyms-problem/9794/2 "2012-11-22T16:47:20Z")
Hi, Not sure what you mean by your first paragraph. The stopwords.txt file needs to exist on every node in the cluster. The file will not be distributed automatically if it is located only on one server. If the file does exist, perhaps the issue is permissions. Where exactly in the filesystem is the file located? Cheers, Ivan On Thu, Nov 22, 2012 at 8:04 AM, Honjoya [jhonjoya@tray.net.br](mailto:jhonjoya@tray.net.br) wrote: > hi > > I am using Elasticsearch Zen discovery, however I am having trouble in > using custom stopword and synonyms. "first server" contains the files put > in the second that has the files on the disk. > > [error] > > RemoteTransportException [[Punisher] [inet [/ 177.67.118.98:9300]] > [indices / create]]; nested: IndexCreationException [[108099] failed to > create index]; nested: FailedToResolveConfigException [Failed to resolve > path config [/ var / www / html / elasticsearch\_api / current / config / > stopwords.txt] tried file path [/ var / www / html / elasticsearch\_api / > current / config / stopwords.txt], path file [/ usr / local / share / > Elasticsearch / config / var / www / html / elasticsearch\_api / current / > config / stopwords.txt], and classpath]; > > Server 1 - Setup > > discovery.zen.ping.timeout: 3s > discovery.zen.ping.multicast.enabled: false > discovery.zen.ping.unicast.hosts: ["192.168.1.102:9200"] > > Server 2 - setup default. > > There Any solution? > > -- -- ---
**Author:** ![Honjoya\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/honjoya_2/32/2576_2.png) [@Honjoya\_2](https://discuss.elastic.co/u/Honjoya_2)\ **Post date:** [November 22, 2012, 5:01pm UTC](https://discuss.elastic.co/t/zen-discovery-stop-words-and-synonyms-problem/9794/3 "2012-11-22T17:01:58Z")
Thanks ... I stopped the second server .The indexing in the first server running normally. When I try to create the index with the second server started - I have this problem . The server 1 and server 2 are on different machines. Only the first server containing the file stopword.txt in /usr/local/share/Elasticsearch/conf/stopword.txt . The Elasticsearch can not replicate it to the second server? need to replicate it manually? Em quinta-feira, 22 de novembro de 2012 14h47min23s UTC-2, Ivan Brusic escreveu: > Hi, > > Not sure what you mean by your first paragraph. The stopwords.txt file > needs to exist on every node in the cluster. The file will not be > distributed automatically if it is located only on one server. > > If the file does exist, perhaps the issue is permissions. Where exactly in > the filesystem is the file located? > > Cheers, > > Ivan > > On Thu, Nov 22, 2012 at 8:04 AM, Honjoya \ > > > wrote: > > > hi > > > > I am using Elasticsearch Zen discovery, however I am having trouble in > > using custom stopword and synonyms. "first server" contains the files put > > in the second that has the files on the disk. > > > > [error] > > > > RemoteTransportException [[Punisher] [inet [/ 177.67.118.98:9300]] > > [indices / create]]; nested: IndexCreationException [[108099] failed to > > create index]; nested: FailedToResolveConfigException [Failed to resolve > > path config [/ var / www / html / elasticsearch\_api / current / config / > > stopwords.txt] tried file path [/ var / www / html / elasticsearch\_api / > > current / config / stopwords.txt], path file [/ usr / local / share / > > Elasticsearch / config / var / www / html / elasticsearch\_api / current / > > config / stopwords.txt], and classpath]; > > > > Server 1 - Setup > > > > discovery.zen.ping.timeout: 3s > > discovery.zen.ping.multicast.enabled: false > > discovery.zen.ping.unicast.hosts: ["192.168.1.102:9200"] > > > > Server 2 - setup default. > > > > There Any solution? > > > > -- -- ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [November 22, 2012, 5:04pm UTC](https://discuss.elastic.co/t/zen-discovery-stop-words-and-synonyms-problem/9794/4 "2012-11-22T17:04:28Z")
Yes, the file needs to be replicated manually. On Thu, Nov 22, 2012 at 9:01 AM, Honjoya [jhonjoya@tray.net.br](mailto:jhonjoya@tray.net.br) wrote: > Thanks ... > > I stopped the second server .The indexing in the first server running > normally. > When I try to create the index with the second server started - I have > this problem . The server 1 and server 2 are on different machines. > > Only the first server containing the file stopword.txt in > /usr/local/share/Elasticsearch/conf/stopword.txt . The Elasticsearch can > not replicate it to the second server? > > need to replicate it manually? > > Em quinta-feira, 22 de novembro de 2012 14h47min23s UTC-2, Ivan Brusic > escreveu: > > > Hi, > > > > Not sure what you mean by your first paragraph. The stopwords.txt file > > needs to exist on every node in the cluster. The file will not be > > distributed automatically if it is located only on one server. > > > > If the file does exist, perhaps the issue is permissions. Where exactly > > in the filesystem is the file located? > > > > Cheers, > > > > Ivan > > > > On Thu, Nov 22, 2012 at 8:04 AM, Honjoya [jhon...@tray.net.br](mailto:jhon...@tray.net.br) wrote: > > > > > hi > > > > > > I am using Elasticsearch Zen discovery, however I am having trouble in > > > using custom stopword and synonyms. "first server" contains the files put > > > in the second that has the files on the disk. > > > > > > [error] > > > > > > RemoteTransportException [[Punisher] [inet [/ 177.67.118.98:9300]] > > > [indices / create]]; nested: IndexCreationException [[108099] failed to > > > create index]; nested: FailedToResolveConfigException [Failed to resolve > > > path config [/ var / www / html / elasticsearch\_api / current / config / > > > stopwords.txt] tried file path [/ var / www / html / elasticsearch\_api / > > > current / config / stopwords.txt], path file [/ usr / local / share / > > > Elasticsearch / config / var / www / html / elasticsearch\_api / current / > > > config / stopwords.txt], and classpath]; > > > > > > Server 1 - Setup > > > > > > discovery.zen.ping.timeout: 3s > > > discovery.zen.ping.multicast.\*\*enabled: false > > > discovery.zen.ping.unicast.\*\*hosts: ["192.168.1.102:9200"] > > > > > > Server 2 - setup default. > > > > > > There Any solution? > > > > > > -- > > > > -- -- ---
**Author:** ![Honjoya\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/honjoya_2/32/2576_2.png) [@Honjoya\_2](https://discuss.elastic.co/u/Honjoya_2)\ **Post date:** [November 22, 2012, 5:06pm UTC](https://discuss.elastic.co/t/zen-discovery-stop-words-and-synonyms-problem/9794/5 "2012-11-22T17:06:51Z")
Thanks... Em quinta-feira, 22 de novembro de 2012 15h04min32s UTC-2, Ivan Brusic escreveu: > Yes, the file needs to be replicated manually. > > On Thu, Nov 22, 2012 at 9:01 AM, Honjoya \ > > > wrote: > > > Thanks ... > > > > I stopped the second server .The indexing in the first server running > > normally. > > When I try to create the index with the second server started - I have > > this problem . The server 1 and server 2 are on different machines. > > > > Only the first server containing the file stopword.txt in > > /usr/local/share/Elasticsearch/conf/stopword.txt . The Elasticsearch can > > not replicate it to the second server? > > > > need to replicate it manually? > > > > Em quinta-feira, 22 de novembro de 2012 14h47min23s UTC-2, Ivan Brusic > > escreveu: > > > > > Hi, > > > > > > Not sure what you mean by your first paragraph. The stopwords.txt file > > > needs to exist on every node in the cluster. The file will not be > > > distributed automatically if it is located only on one server. > > > > > > If the file does exist, perhaps the issue is permissions. Where exactly > > > in the filesystem is the file located? > > > > > > Cheers, > > > > > > Ivan > > > > > > On Thu, Nov 22, 2012 at 8:04 AM, Honjoya [jhon...@tray.net.br](mailto:jhon...@tray.net.br) wrote: > > > > > > > hi > > > > > > > > I am using Elasticsearch Zen discovery, however I am having trouble in > > > > using custom stopword and synonyms. "first server" contains the files put > > > > in the second that has the files on the disk. > > > > > > > > [error] > > > > > > > > RemoteTransportException [[Punisher] [inet [/ 177.67.118.98:9300]] > > > > [indices / create]]; nested: IndexCreationException [[108099] failed to > > > > create index]; nested: FailedToResolveConfigException [Failed to resolve > > > > path config [/ var / www / html / elasticsearch\_api / current / config / > > > > stopwords.txt] tried file path [/ var / www / html / elasticsearch\_api / > > > > current / config / stopwords.txt], path file [/ usr / local / share / > > > > Elasticsearch / config / var / www / html / elasticsearch\_api / current / > > > > config / stopwords.txt], and classpath]; > > > > > > > > Server 1 - Setup > > > > > > > > discovery.zen.ping.timeout: 3s > > > > discovery.zen.ping.multicast.\*\*enabled: false > > > > discovery.zen.ping.unicast.\*\*hosts: ["192.168.1.102:9200"] > > > > > > > > Server 2 - setup default. > > > > > > > > There Any solution? > > > > > > > > -- > > > > > > -- -- ---
**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, 3:03am UTC](https://discuss.elastic.co/t/zen-discovery-stop-words-and-synonyms-problem/9794/6 "2017-07-06T03:03:15Z")