# Issue Mapping Elasticsearch **URL:** \ **Category:** Elasticsearch\ **Created:** [July 15, 2014, 9:15pm UTC](https://discuss.elastic.co/t/issue-mapping-elasticsearch/18684 "2014-07-15T21:15:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![asal\_masuk](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@asal\_masuk](https://discuss.elastic.co/u/asal_masuk)\ **Post date:** [July 15, 2014, 9:15pm UTC](https://discuss.elastic.co/t/issue-mapping-elasticsearch/18684/1 "2014-07-15T21:15:30Z")
Hey, I am using ELK stack for log processing. Logstash 1.4.2 (Single Instance) and Elasticsearch 1.2.2(Cluster of 2 nodes), and redis as broker between logstash and elasticsearch. I am able to parse my logs using Logstash, get the parsed document in Redis. But not able to get the documents inside Elasticsearch. The following is my Central logstash server configuration file. _input { redis { host =\> "xx.xx.xx.xx" type =\> "redis-input" data\_type =\> "list" key =\> "logstash" threads =\> 5} redis { host =\> "xx.xx.xx.xx" type =\> "redis-input" data\_type =\> "list" key =\> "logstash" threads =\> 5}} filter { date { match =\> ["timestamp\_nsstats",%{YEAR}-%{MONTHNUM}-%{MONTHDAY}[,]%{HOUR}:?%{MINUTE}(?::?%{SECOND})?"] } } output { stdout { } elasticsearch { cluster =\> "logstash" host =\> "xx.xx.xx.xx" protocol =\> "http" node\_name =\> "Node1" index =\> "logstash-%{+YYYY.MM.dd}"} }_ The following is the health of Elasticsearch Instances. 1. { 2. "cluster\_name": "logstash", 3. "status": "green", 4. "timed\_out": false, 5. "number\_of\_nodes": 2, 6. "number\_of\_data\_nodes": 2, 7. "active\_primary\_shards": 3, 8. "active\_shards": 6, 9. "relocating\_shards": 0, 10. "initializing\_shards": 0, 11. "unassigned\_shards": 0 12. } I am not able to find out the reason, that is causing logstash being not able to reach elasticsearch. Do I need to make any changes in configuration file, which might make logstash aware of the elasticsearch server. Please let me know what you think, that might be causing the issue. If you need any other information please let me know. Thank you -- 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/CAKKFHoG3\_rY%3Dtx6x7ibmXVRk7btXw\_Xaxv\_S-FEMHX0b\_g8-oA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKKFHoG3_rY%3Dtx6x7ibmXVRk7btXw_Xaxv_S-FEMHX0b_g8-oA%40mail.gmail.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:** [July 15, 2014, 10:22pm UTC](https://discuss.elastic.co/t/issue-mapping-elasticsearch/18684/2 "2014-07-15T22:22:11Z")
You should probably start this conversation on the logstash list. However if you are using the http output then you don't need cluster or node\_name. It'd be worth testing that you can telnet from your LS host to your ES host on port 9200, and also try enabling verbose logging in LS with -v. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 16 July 2014 07:15, Voc Austin [vocasal@gmail.com](mailto:vocasal@gmail.com) wrote: > Hey, > > I am using ELK stack for log processing. Logstash 1.4.2 (Single Instance) > and Elasticsearch 1.2.2(Cluster of 2 nodes), and redis as broker between > logstash and elasticsearch. > > I am able to parse my logs using Logstash, get the parsed document in > Redis. But not able to get the documents inside Elasticsearch. > > The following is my Central logstash server configuration file. > > _input { redis { host =\> "xx.xx.xx.xx" type =\> > "redis-input" data\_type =\> "list" key =\> "logstash" > threads =\> 5 } redis { host =\> "xx.xx.xx.xx" type =\> > "redis-input" data\_type =\> "list" key =\> "logstash" > threads =\> 5 }} filter { date { match =\> > ["timestamp\_nsstats",%{YEAR}-%{MONTHNUM}-%{MONTHDAY}[,]%{HOUR}:?%{MINUTE}(?::?%{SECOND})?"] > } } output { stdout { } elasticsearch > { cluster =\> "logstash" host =\> > "xx.xx.xx.xx" protocol =\> "http" node\_name =\> > "Node1" index =\> "logstash-%{+YYYY.MM.dd}"} }_ > The following is the health of Elasticsearch Instances. > > 1. { > > 2. "cluster\_name": "logstash", > > 3. "status": "green", > > 4. "timed\_out": false, > > 5. "number\_of\_nodes": 2, > > 6. "number\_of\_data\_nodes": 2, > > 7. "active\_primary\_shards": 3, > > 8. "active\_shards": 6, > > 9. "relocating\_shards": 0, > > 10. "initializing\_shards": 0, > > 11. "unassigned\_shards": 0 > > 12. } > > I am not able to find out the reason, that is causing logstash being not able to reach elasticsearch. Do I need to make any changes in configuration file, which might make logstash aware of the elasticsearch server. > > Please let me know what you think, that might be causing the issue. If you need any other information please let me know. > > Thank you > > -- > 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/CAKKFHoG3\_rY%3Dtx6x7ibmXVRk7btXw\_Xaxv\_S-FEMHX0b\_g8-oA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKKFHoG3_rY%3Dtx6x7ibmXVRk7btXw_Xaxv_S-FEMHX0b_g8-oA%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAKKFHoG3\_rY%3Dtx6x7ibmXVRk7btXw\_Xaxv\_S-FEMHX0b\_g8-oA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAKKFHoG3_rY%3Dtx6x7ibmXVRk7btXw_Xaxv_S-FEMHX0b_g8-oA%40mail.gmail.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/CAEM624befEXSocmRZo-rniVkoeP%3DpgO0YLwHS-m%3Dmb1EAeZNow%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624befEXSocmRZo-rniVkoeP%3DpgO0YLwHS-m%3Dmb1EAeZNow%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![shriyansh\_jain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shriyansh_jain/32/1035_2.png) [@shriyansh\_jain](https://discuss.elastic.co/u/shriyansh_jain)\ **Post date:** [July 15, 2014, 11:18pm UTC](https://discuss.elastic.co/t/issue-mapping-elasticsearch/18684/3 "2014-07-15T23:18:05Z")
Hey I started the conversation on logstash list as suggested by you. I tried testing to telnet from the Logstash central server to ES server. Following is the output I am getting. $ telnet 10.12.7.2 9200 Trying 10.12.7.2... Connected to xxxxxxxxxxxx (10.12.7.2). Escape character is '^]'. Here is the link to the discussion, [https://groups.google.com/forum/#!topic/logstash-users/9IPSEtCwrNc](https://groups.google.com/forum/#!topic/logstash-users/9IPSEtCwrNc) Any input will be greatly appreciated. -Shriyansh On Tuesday, July 15, 2014 3:22:43 PM UTC-7, Mark Walkom wrote: > You should probably start this conversation on the logstash list. > However if you are using the http output then you don't need cluster or > node\_name. It'd be worth testing that you can telnet from your LS host to > your ES host on port 9200, and also try enabling verbose logging in LS with > -v. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \ > web: [www.campaignmonitor.com](http://www.campaignmonitor.com) > > On 16 July 2014 07:15, Voc Austin \<[voc...@gmail.com](mailto:voc...@gmail.com) \\> wrote: > > > Hey, > > > > I am using ELK stack for log processing. Logstash 1.4.2 (Single Instance) > > and Elasticsearch 1.2.2(Cluster of 2 nodes), and redis as broker between > > logstash and elasticsearch. > > > > I am able to parse my logs using Logstash, get the parsed document in > > Redis. But not able to get the documents inside Elasticsearch. > > > > The following is my Central logstash server configuration file. > > > > _input { redis { host =\> "xx.xx.xx.xx" type =\> > > "redis-input" data\_type =\> "list" key =\> "logstash" > > threads =\> 5 } redis { host =\> "xx.xx.xx.xx" type =\> > > "redis-input" data\_type =\> "list" key =\> "logstash" > > threads =\> 5 }} filter { date { match =\> > > ["timestamp\_nsstats",%{YEAR}-%{MONTHNUM}-%{MONTHDAY}[,]%{HOUR}:?%{MINUTE}(?::?%{SECOND})?"] > > } } output { stdout { } elasticsearch > > { cluster =\> "logstash" host =\> > > "xx.xx.xx.xx" protocol =\> "http" node\_name =\> > > "Node1" index =\> "logstash-%{+YYYY.MM.dd}"} }_ > > The following is the health of Elasticsearch Instances. > > > > 1. { > > > > 2. "cluster\_name": "logstash", > > > > 3. "status": "green", > > > > 4. "timed\_out": false, > > > > 5. "number\_of\_nodes": 2, > > > > 6. "number\_of\_data\_nodes": 2, > > > > 7. "active\_primary\_shards": 3, > > > > 8. "active\_shards": 6, > > > > 9. "relocating\_shards": 0, > > > > 10. "initializing\_shards": 0, > > > > 11. "unassigned\_shards": 0 > > > > 12. } > > > > I am not able to find out the reason, that is causing logstash being not able to reach elasticsearch. Do I need to make any changes in configuration file, which might make logstash aware of the elasticsearch server. > > > > Please let me know what you think, that might be causing the issue. If you need any other information please let me know. > > > > Thank you > > > > -- > > 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/CAKKFHoG3\_rY%3Dtx6x7ibmXVRk7btXw\_Xaxv\_S-FEMHX0b\_g8-oA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKKFHoG3_rY%3Dtx6x7ibmXVRk7btXw_Xaxv_S-FEMHX0b_g8-oA%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAKKFHoG3\_rY%3Dtx6x7ibmXVRk7btXw\_Xaxv\_S-FEMHX0b\_g8-oA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAKKFHoG3_rY%3Dtx6x7ibmXVRk7btXw_Xaxv_S-FEMHX0b_g8-oA%40mail.gmail.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/e6605cd3-8571-47ae-b4fc-f3bce5af7fa9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e6605cd3-8571-47ae-b4fc-f3bce5af7fa9%40googlegroups.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, 1:15am UTC](https://discuss.elastic.co/t/issue-mapping-elasticsearch/18684/4 "2017-07-06T01:15:36Z")