discovery fixed policy breaks if service stays down for extended period

Discovery has fixed policy for service assignment in which services are assigned to consumers in a fixed, static or constant manner. For example if there are "n" publishers of a service and there are "m" consumers that are interested in "k" instances (say 2) of service, then all "m" consumers will get <n0, n1, n2 ... nk> service instances. This is akin to priority order. If an instance, say "ni" such that 0 <= i <= k went down for an extended period (> 15 seconds) and comes back up, it should no longer be assigned to a new consumer because it should go to the bottom of the prioritized list. It should not retain its position. Current behavior of discovery does not match this expectation and "ni" service continues to get assigned to new consumers.