upthewaterspout commented on pull request #6714: URL: https://github.com/apache/geode/pull/6714#issuecomment-956863658
> I'm wondering if someone would have a reason to specify an IP address as the bind address that this might break. Cases I could think about: > > * Maybe there is no DNS name? The call to `getHost()` might fail > > * Maybe the DNS server isn't updated at the time the member starts. This might be the case in a IaaS where VMs or containers are launched as soon as the gemfire process starts. I guess for this case an old member would be less likely to not be resolvable? > > > I'm not sure if this should reject this approach or not, if there are no better options. Or maybe we just failures from getHost and retain the IP address. I wonder if it would be possible to fall back to the old logic for hostname validation if the member is from an old member, rather than changing the bind address when deserializing. Would that be doable or any safer? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
