Disk Watermark issues with 1.4.0

Hi all, I'm running 1.4.0. and using the default settings for: cluster.routing.allocation.disk.watermark.low and cluster.routing.allocation.disk.watermark.high I hit an OOME which caused me to need to cycle a node, and then all shards that should live on that node stayed unallocated once I

Re: Disk Watermark issues with 1.4.0

On Mon, Dec 1, 2014 at 11:28 AM, Chris Neal chris.n...@derbysoft.net wrote: Hi all, I'm running 1.4.0. and using the default settings for: cluster.routing.allocation.disk.watermark.low and cluster.routing.allocation.disk.watermark.high I hit an OOME which caused me to need to cycle a

Re: Disk Watermark issues with 1.4.0

Thanks for the quick reply Nik :) I've got updating to 1.4.1 on my TODO list for today, as I see there were some updates in the Release notes pertaining to this as well. I might let things fill up again in Dev and see what happens. Maybe I wasn't patient enough for the rerouting to start on its