Java Client integration with Jetty Plugin
Hi I am using Elasticsearch version 1.2.1. I was looking for ways to secure access to Elasticsearch when I found the Jetty plugin. It lets me create users based on roles and is satisfying my requirements. However it only restricts HTTP requests. I was using Java Transport client for talking to Elasticsearch and since it uses Transport layer protocol while connecting to ES at 9300, the Jetty plugin has no effect on it. So as an alternative to the Transport Client I have tried using the Jest Client. But I have not found any API for sending authentication credentials while inserting data or reading or when creating a client. Is there a way in which I can pass authentication credentials in the Jest client while sending requests? If Jest Client does not support this, are there any alternative clients which will allow me to do so? Any help on this would be appreciated. Regards Mihir - Regards -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Java-Client-integration-with-Jetty-Plugin-tp4063253.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1410346337441-4063253.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout.
Increase in Indexing Time and big Merges
Hi, We have an ES cluster of 7 nodes in our development environment. 3 of which are Master nodes and the rest 4 are Data nodes. Masters run with default heap and Data nodes with 4 GB heap on 8 GB RAM machines. We do bulk inserts continuously and simultaneously fire aggregation queries every minute. We maintain day-wise indices with 5 shards and 1 replica. Our bulk count is 1500 docs and bulk size is 370 KB approx. So our everyday's index size amounts to 35 GB approx. We are observing insertions slowing down due to increase in indexing time, which reaches to about 6-7 sec. This is observed after 12-13 hours of insertions into an index. The behaviour repeats for every index. Also, we observe Merges as high as 16 GB on some data nodes during the same time. In the Index stats the merges are seen to around 32 GB. This is seen to affect the overall performance of ES. We have tried various merge level settings like increasing segments_per_tier(to 15), reducing index.store.throttle.max_bytes_per_sec to something like 10 MB and reducing merge.policy.max_merged_segment to 2GB. These have managed to reduce big merges, but indexing time increase is still observed. Please guide us on ways to have consistent indexing time and insertion rate, and how to minimize the effects of Merging. Thanks Mihir - Regards -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Increase-in-Indexing-Time-and-big-Merges-tp4055918.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1400132247263-4055918.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout.
Re: SearchParseExceptions in Marvel monitoring cluster
Thanks Boaz for your reply. Following is the output of curl SERVER:9200/_cat/shards/?v for both nodes of our marvel cluster: index shard prirep state docs storeip node .marvel-2014.05.01 0 p STARTED 70 865.4kb Server-ip-1 Marvel_1 .marvel-2014.05.01 0 r STARTED 70 865kbServer-ip-2 Marvel_2 Some more things to highlight, in the Marvel Dashboard - Cluster Overview page we get following errors : - Oops! FacetPhaseExecutionException[Facet [0]: (value) field [total.search.query_total] not found] --- in the Search Request Rate panel - Oops! FacetPhaseExecutionException[Facet [timestamp]: failed to find mapping for index.raw] --- in the Indices panel - Oops! FacetPhaseExecutionException[Facet [0]: (value) field [primaries.indexing.index_total] not found] --- in the Indexing Request Rate panel - Oops! FacetPhaseExecutionException[Facet [0]: (value) field [primaries.docs.count] not found] --- in the Document Count Panel All these apart from the SearchParseExceptions mentioned in earlier post. Also if Marvel is not storing the right data, how is it supposed to be handled? - Regards -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/SearchParseExceptions-in-Marvel-monitoring-cluster-tp4054926p4055150.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1398919064490-4055150.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout.
