Re: What to do if ES document count continuously increases - with zero indexing ongoing

he cluster, uninstalling Marvel, and starting master-only nodes followed by data-only nodes. Regards,Swaroop 12.03.2014, 16:18, "Clinton Gormley" cl...@traveljury.com:Have you looked at the docs? http://www.elasticsearch.org/guide/en/marvel/current/index.html#configurationOn 12 March 2014 06:4

What to do if ES document count continuously increases - with zero indexing ongoing

Hello, We have bulk-indexed a fresh ES 1.0.1 cluster with index.refresh_interval : -1 (disabled), and then set index.refresh_interval: 5s about 20 hours ago, the document count is continuously increasing since then, is this normal or expected? How do I know when it'll be done? Our expected

DELETE snapshot request (which was long-running and had not yet completed) is hung

Hi, I had started a snapshot request on a freshly-indexed ES 1.0.1 cluster with cloud plugin installed, but unfortunately the EC2 access keys configured did not have S3 permissions, so ES was in a weird state, so I sent a DELETE snapshot request and it's stuck for more than a couple of hours,

Re: DELETE snapshot request (which was long-running and had not yet completed) is hung

 Hi Igor, It seems that the S3 bucket had "PUT only permissions". Regards,Swaroop  10.03.2014, 17:40, "Igor Motov" imo...@gmail.com:That's strange. Wrong S3 permissions should have caused it to failed immediately. Could you provide any more details about the permissions, so I can reproduce it?

After bulk indexing with refresh_interval disabled, now at 100% CPU usage for 24 hours

Hello, We have a brand-new ES 1.0.1 cluster of 3 m2.xlarge machines, we set `index.refresh_interval` to -1, `index.number_of_replicas` to 0, `index.number_of_shards` to 10 and indexed about half a million documents in about 2000 indexes, this completed successfully in about 10 hours. However,

Re: After bulk indexing with refresh_interval disabled, now at 100% CPU usage for 24 hours

For posterity note, the problem was solved by specifying {index.refresh_interval: 5s} - note the s : by specifying just 5, ES assumes 5 milliseconds! Regards, Swaroop 07.03.2014, 11:28, Swaroop CH swaroo...@yandex.com: Hello, We have a brand-new ES 1.0.1 cluster of 3 m2.xlarge machines