You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
neilstevenson
added a commit
to hazelcast/hazelcast-platform-demos
that referenced
this issue
Jan 7, 2020
On
com.hazelcast:hazelcast:4.0-SNAPSHOT
withcom.hazelcast:hazelcast-kubernetes:2.0
if a stateful set and a service are created in the same YAML, false warnings appear about the service
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
The text was updated successfully, but these errors were encountered: