SaadKhanBackendDeveloper
commented
9 years ago Adding more information that might help some one to suggest something.
My server specs are: 2 Cores CPU 2 GB RAM 40GB HardDisk I am using 3 separate VPS for data clustering. All having same specs and running only ElasticSearch on them. They are CentOS VPS.
and
Size of data is: 186MB (190192 KB to be exact)
jprante
I have setup an ElasticSearch river with 20 minutes interval. Here is the river defination:
{ "type": "jdbc", "jdbc": { "driver": "com.microsoft.sqlserver.jdbc.SQLServerDriver", "url": "jdbc:sqlserver://server;databaseName=DBName", "user": "user", "password": "pass", "sql": "select * from table", "index": "indexname", "type": "typename", "autocommit": true, "strategy": "simple", "schedule": "0 0/20 * 1/1 * ? *" } } River is executing successfully with 20 mints interval. But when river executes it only runs for 3 mints and does not fetch all records. I have around 3.3Million records in my table and on every execution of river it fetches around 0.3-0.5 million records (in 3 mints) and then stopped.
My question is why river stops after 3 mints? River still has 17 more mints from its next run, it should execute for next 17 mints or until all records are fetched.
Any help will be highly appreciated. Thanks
Note: I am checking river status from BigDesk and "status" flag which sets to true when river starts execution.