Look at the Java API<http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/>. >From my look through elasticsearch code, it does not generate HTTP requests but routes them through services.
How many logs do you generate on average? Do your servers have enough resources to handle indexing and searching at the same time? I think you should worry about these questions more than HTTP loading on your server. Additionally logging messages from a web application to elasticsearch in the same webapp requires some thought into implementation; you can wind up in an endless loop if a class that saves your logs to elasticsearch also logs a message. Another item to think about is how to index the logs and how long to retain them. On Monday, February 10, 2014 10:58:59 AM UTC-5, Doru Sular wrote: > > Hi guys, > > I intend to use the elasticsearch embedded in my webapplication. > Is there a kind of optimization for rest calls (for indexing a document > for example) to not generate http traffic, when the elasticsearch is > running in same virtual machine as the service caller? (Instead of generate > an http request, just use java objects) > Is there a way to index a document without using the rest api, in case the > elasticsearch is embedded in the same webapplication? > I want to index the log messages from my application as soon they are > produced, but we have a lot of messages, should I be concerned of the http > loading on the server? > > Thank you very much, > Doru > -- 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/c0f60c04-a939-4ea8-aade-e3781a54cafb%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
