Skip to content
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.

False warnings about service missing #185

Open
neilstevenson opened this issue Jan 7, 2020 · 0 comments
Open

False warnings about service missing #185

neilstevenson opened this issue Jan 7, 2020 · 0 comments

Comments

@neilstevenson
Copy link

On com.hazelcast:hazelcast:4.0-SNAPSHOT with com.hazelcast:hazelcast-kubernetes:2.0
if a stateful set and a service are created in the same YAML, false warnings appear about the service

12:55:55.603 [main] WARN  com.hazelcast.spi.discovery.integration.DiscoveryService - [10.48.2.5]:5701 [xxx] [4.0-SNAPSHOT] DNS lookup for serviceDns 'yyy-service.default.svc.cluster.local' failed: name not found

This seems to be a race condition, the service is still being created. The 2nd pod finds it.

If we suppress this warning, we hide real problems finding the service name.

Also, if the DNS lookup fails, this should be an error not a warning

neilstevenson added a commit to hazelcast/hazelcast-platform-demos that referenced this issue Jan 7, 2020
@leszko leszko added this to the 2.1 milestone Jan 9, 2020
@leszko leszko removed this from the 2.1 milestone Nov 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants