Tag Info

New answers tagged

0

Beside open port on your firewall you will need Access-Control-Allow-Origin headers. A configuration for nginx might look like this: server { listen 80; location / { proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header ...


0

You can also change the mapping (or template, which generates a mapping) to remove the _source field. http://www.elastic.co/guide/en/elasticsearch/reference/master/mapping-source-field.html Also, the space increase is more efficient in newver versions. ... oh, and are you looking at the total size (inclusing any replicas)


0

No route to host these days often can mean that you are getting an ICMP Administratively Prohibited message -- ie. you are being denied by firewall. They are particularly common on Red Hat systems, from what I have seen, but I would hope that you see them elsewhere too. This makes it easier to differentiate from Connection Refused (which would just mean ...


1

When it happens next check free - m and monitor the Elasticsearch logs at /var/log/elasticsearch/your cluster name.log. - ugh, this was supposed to be a comment but the Android app made it an answer...


1

Usual solution (as far as I know and certainly what I've implemented) is combination of iptables (to restrict direct access) and then providing access via reverse proxy in Apache, Nginx, your web server of choice. Web search for "securing elasticsearch" brings up plenty of relevant stuff. Depends exactly what you're tryng to do whether reverse proxy is ...


0

Check to see that the logs per second at your final endpoint (e.g. elasticsearch) are above some baseline. That is, do an end to end check, if your end result is working correctly, you know that all the steps in the pipeline work correctly. If you frequently have problems, or need better introspection, start instrumenting each piece of the pipeline like ...



Top 50 recent answers are included