Check for minHosts > Available hosts in HostAvailabilityListener

[srinathgit]

We don't do any checks if minHosts > Available hosts in cluster . I am not sure if we have to do that check. But, I am opening this bug just in case if we choose to do it.

This HostAvailabilityListener is created even though the server is a single node instance

failure.add( new HostAvailabilityListener(dmManager)
						.withSuspendTimeForHostUnavailable(Duration.ofSeconds(15))
						.withMinHosts(5));

[vivekmuniyandi]

The last time I spoke to Sam, he was a bit hesitant about the minHosts functionality and he said it is a functionality that is not so important. Validating this would have to call the forestInfo endpoint and throwing an error if the minHosts is greater than the number of hosts. So, I don't think this is necessary but I will check with Sam if he also feels the same way.

[sammefford]

What error do you get when you do this? I'm guessing it says that the job was stopped because the number of hosts is less than minHosts. Seems to me that addresses the issue because we're doing what they told us to do and telling them why we did it.

[srinathgit]

Sam,

The issue I mentioned is when creating an instance of HostAvailabilityListener. When instantiating, we don't check if available host > minHosts. We check only when the list of exceptions is thrown during job run.