Re: encountered monitor.jvm warning

gt; hth > > jason > > On Tue, Mar 24, 2015 at 11:59 PM, Abid Hussain > > wrote: > > All settings except from ES_HEAP (set to 10 GB) are defaults, so I > actually > > am not sure about the new gen setting. > > > > The host has 80 GB memory in total a

Re: encountered monitor.jvm warning

etting? how much is the system memory in total? > how many cpu cores in the node? what query do you use? > > jason > > On Tue, Mar 24, 2015 at 5:26 PM, Abid Hussain > > wrote: > > Hi all, > > > > we today got (for the first time) warning messages which s

encountered monitor.jvm warning

Hi all, we today got (for the first time) warning messages which seem to indicate a memory problem: [2015-03-24 09:08:12,960][WARN ][monitor.jvm ] [Danger] [gc][young][413224][18109] duration [5m], collections [1]/[5.3m], total [5m]/[16.7m], memory [7.9gb]->[3.7gb]/[9.8gb], all_poo

Index and find emails using pre- and postfix wildcards

Hi all, I'm looking for an easy way to index documents containing an email field and searching for them using pre- and postfix wildcard queries (something similar to SQL: WHERE email LIKE '%search_term%'). One way may be using the uax_url_email tokenizer but it seems that in this case prefix w

Re: Limit large number of threads

Thanks Jörg, I did a thread dump: 60 % of ~400 threads are in state WAITING, 35 % are in state RUNNABLE, the rest is in state TIMED_WAITING, none is in state BLOCKED. So I assume everything is OK - still wondering whats the point of creating hundreds of threads as there are "only" 24 cores avai

Re: Limit large number of threads

ut of bounds, it may be a lockup somewhere. What > version of ES do you use? > > Jörg > > On Fri, Mar 20, 2015 at 2:08 PM, Abid Hussain > wrote: > >> Thanks for clarification. >> >> Still I wonder why such a huge amount of thread is created and if this >>

Re: Limit large number of threads

not show all internal thread pools in ES now. > > Regards, > Lukas > > On Fri, Mar 20, 2015 at 10:56 AM, Abid Hussain > wrote: > >> Hi all, >> >> I know I'm not the first one wondering about the number of threads but I >> didn't find anything

Limit large number of threads

Hi all, I know I'm not the first one wondering about the number of threads but I didn't find anything really appropriate to my question. We use ES with the default values for the thread pool sizes, that is actually (according to what bigdesk says): * Search 72 * Index 24 * Bulk 24 * Refresh 10

Java API TransportClient Threadpool

Hi all, I would like to understand how TransportClient works in terms of how it uses it's thread pool. - As it uses a threadpool I assume that every request is performed in it's own thread - is that correct? - If so, does that mean that i.e. it's pool size is 20 and 21 search reque

Re: Queue Size limited?

s where many rivers are active. > > Jörg > > On Mon, Feb 23, 2015 at 9:40 AM, Abid Hussain > wrote: > >> Hi all, >> >> last restart of our cluster caused a heavy load as a couple of rivers are >> triggered which load alltogether about 40 GB of data into the

Queue Size limited?

Hi all, last restart of our cluster caused a heavy load as a couple of rivers are triggered which load alltogether about 40 GB of data into the (single-node) cluster. This lead to massive exceptions like shown in the logs: [6726]: index [my_index], type [my_doc_type], id [2390342], message [Es

How to wait for changes to be comitted?

Hi all, In one of our integration test we do the following: 1. create an index 2. put some docs in the created index 3. assert that documents exist in index Step 3 sometimes fails if we don't put a Thread.sleep(1000) between 2 and 3. After reading the docs, I think performing a FlushRe

Re: jdbc river keeping connection open

+1 schrieb Abid Hussain: > > Are you sure the deletion of a (non-existent) mapping "_river" makes sense? >> > The given code results in river deletion. If there is a better way to do > so, I would be happy if you could tell me. > > >> What connection i

Re: jdbc river keeping connection open

connection used by river remains open. Regards, Abid > Jörg > Am 16.02.2015 12:29 schrieb "Abid Hussain" >: > >> Hi all, >> >> we have some JUnit based integration tests in which we basically setup a >> clean system, create a river and do some i

jdbc river keeping connection open

Hi all, we have some JUnit based integration tests in which we basically setup a clean system, create a river and do some index operations like inserting/updating documents. We are not using ElasticSearchIntegrationTest but are running our tests against a dedicated cluster. In the setup which

Re: real one shot jdbc river

So I tried the oneshot strategy with no success. The river is being rerun after restart of cluster. Am Donnerstag, 12. Februar 2015 15:22:27 UTC+1 schrieb Abid Hussain: > > Hi all, > > we run a jdbc river once per night for a complete recreation of our index. > > The river

real one shot jdbc river

Hi all, we run a jdbc river once per night for a complete recreation of our index. The river - once it has been created - will run again after a restart of elasticsearch cluster (single node cluster). But what we try to achieve is a one shot river, which isn't being re-run after restart of clus

Re: jdbc river won't start

0/_river/my_river/' > > before creating the new river with same name? I see there is '_version: > 12', this means, you did not stop the old river instance with DELETE. > > Jörg > > On Wed, Feb 11, 2015 at 2:38 PM, Abid Hussain > wrote: > >> Hi, >> &g

jdbc river won't start

Hi, we are running ES on a single node cluster. I'm facing the issue that a river is not being started after being re-created. In detail, we first delete the index the river refers to, then delete the river and then create it again. *GET /_river/my_river/_meta* { "_index": "_river", "_ty

Re: log4j: Configuring SMTPAppender

(directory /home/my_user exists) and I have no idea what I'm doing wrong... :-( Regards, Abid Am Montag, 9. Februar 2015 15:31:01 UTC+1 schrieb Abid Hussain: > > Hi all, > > I'd like to configure a smtpappender in logging.yml so that an email is > sent whe

log4j: Configuring SMTPAppender

Hi all, I'd like to configure a smtpappender in logging.yml so that an email is sent whenever a message is logged. Unfortunately, the yml configuration isn't very well documented on log4j homepage and I wasn't able to find any working example in the www. I also tried to put a separate logging.

Re: Recommended setup for using TransportClient in Webapp

> | @elasticsearchfr > <https://twitter.com/elasticsearchfr> | @scrutmydocs > <https://twitter.com/scrutmydocs> > > > > Le 4 févr. 2015 à 10:12, Abid Hussain > a écrit : > > Hi all, > > I wonder what is the recommended setup for using TransportC

Recommended setup for using TransportClient in Webapp

Hi all, I wonder what is the recommended setup for using TransportClient in a multi-threaded environment with parallel search requests (i.e. a webapp). Basically, I see two alternatives: 1. Using a single instance of TransportClient for all incoming search requests 2. Creating a new i

Re: Obtain jdbc river state via java api

Thanks, so I implement the state request with http get. Regards, Abid Am Montag, 2. Februar 2015 17:50:53 UTC+1 schrieb Jörg Prante: > > There is no stateful river concept in Elasticsearch. > > Jörg > > On Mon, Feb 2, 2015 at 3:57 PM, Abid Hussain > wrote: > >> H

Obtain jdbc river state via java api

Hi all, is there a way to obtain state of a certain river (like *GET /_river/jdbc//_state*) via TransportClient or any other kind of java api call? If not, I would have to perform a http get request programmatically and parse json result, I guess... Regards, Abid -- You received this messa

Re: Connect to standalone node using TransportClient

Thanks to both, David and Jürgen. I used Davids solution which works well for know and keep in mind Jürgens proposal for production installation. Best regards, Abid Am Donnerstag, 29. Januar 2015 09:05:15 UTC+1 schrieb Abid Hussain: > > Hi all, > > I'm running a standalo

Re: Connect to standalone node using TransportClient

; Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 29 janv. 2015 à 14:43, Abid Hussain > a écrit : > > Thanks for help. As you can see in the original quesion above, I already > tried setting node.local: true. > > This works on server side, but I'm not able t

Re: Connect to standalone node using TransportClient

r / @scrutmydocs > > Le 29 janv. 2015 à 14:18, Abid Hussain > a écrit : > > After doing some research, It seems to me that it is not possible to > connect to a node configured as *node.local: true* using TransportClient. > > ... which leads me to the question: >

Re: Connect to standalone node using TransportClient

Donnerstag, 29. Januar 2015 09:05:15 UTC+1 schrieb Abid Hussain: > > Hi all, > > I'm running a standalone node (by using *node.local: true* in > elasticsearch.yml) and want to connect to this node via TransportClient > which fails. > > Connecting to the node via Sense

Connect to standalone node using TransportClient

Hi all, I'm running a standalone node (by using *node.local: true* in elasticsearch.yml) and want to connect to this node via TransportClient which fails. Connecting to the node via Sense succeeds. I didn't change the cluster.name property in elasticsearch.yml. My Code is: Client client = new

Re: How does sorting on _id work?

... can it be that _id is treated as string? If so, is there any way retrieve the max _id field with treating _id as integer? Am Dienstag, 27. Januar 2015 19:24:41 UTC+1 schrieb Abid Hussain: > > Hi all, > > I want to determine the doc with max and min _id value. So, when I run

How does sorting on _id work?

Hi all, I want to determine the doc with max and min _id value. So, when I run this query: GET /my_index/order/_search { "fields": [ "_id" ], "sort": [ { "_uid": { "order": "desc" } } ], "size": 1 } I get a result: { ... "hits": { ... "hits": [ {

Re: jdbc river re-indexing after each start of server?

Thanks for you quick help! Am Montag, 26. Januar 2015 13:15:26 UTC+1 schrieb Jörg Prante: > > You should delete the river instance after usage. Otherwise, the river is > executed each time the node starts. > > Jörg > > On Mon, Jan 26, 2015 at 1:09 PM, Abid Hussain > wro

jdbc river re-indexing after each start of server?

Hi all, I configured a river for one-time indexing like: PUT /_river/my_river/_meta { "type": "jdbc", "jdbc": { "driver": "com.mysql.jdbc.Driver", "url": "jdbc:mysql://192.168.110.180:3306/my_db", "user": "user", "password": "password", "ind

Re: Keeping jdbc river in sync with DB

onal effort. > > Jörg > > On Wed, Jan 21, 2015 at 4:56 PM, Abid Hussain > wrote: > >> Hi all, >> >> I'm trying to figure out how to configure jdbc river in production >> environment. >> >> We want to index a DB with appr. 10% write querie

JDBC river in production environment

Hi all, I'm quite new to ES and wonder how/if jdbc river is ready for indexing RDBMS in production enviromnent as in GitHub it says about River: *about to be deprecated by Elasticsearch core team* So is it a good idea to use

Keeping jdbc river in sync with DB

Hi all, I'm trying to figure out how to configure jdbc river in production environment. We want to index a DB with appr. 10% write queries and 90% read queries and need to keep ES index in sync with DB. So I wonder how two configure river to keep Index in near-realtime Sync with DB. I'm thin