Dont require knownleader

[chrisgray-vertex]

According to hashicorp/consul#9776, the X-Consul-Knownleader is unreliable and is likely to be removed at some point. In current versions of Consul, the value will be false when doing streaming requests. This causes caches to get stale here.

The recommendation from the referenced issue is to not use the X-Consul-Knownleader: for anything.

[windonis]

Hi all,

We need these commits. I wonder that, when will this commit be included in a tag?

Best Regards

[vbashko]

Not a Contribution.

Hi @rickfast, @chrisgray-vertex. It seems that the master build failed after this PR was merged and the change was never released to the maven central repo. Is there a way to re-build the project and release the library including this change?

Thanks!

[aswingit]

@rickfast @chrisgray-vertex Looks like the master build has failed after this PR was merged. Could you please review it? Observing that the "ServiceHealthCache" listener is not getting invoked as consuleResponse.isKnownLeader() is false in ConsulCache.onComplete()

[dlabey]

Any ETA for a release on this? Can you fix the build?

[dlabey]

@rickfast can you manually attempt to kick-off another Jenkins CI action from master?