You really don't want to do that... In the past, when using PostgreSQL and binding it to a subdomain like db.yourdomain.com (just for not having to remember IPs, even it doesn't really matter in code-level) I had experienced randomly and unexpectedly very slow timings and even disconnections for quite some painful time just because DNS servers between were having issues, etc... Using an IP address will never incur in this kind of issue as no hostname translations has to be performed.
I don't see any benefit for doing so. Just use IPs and forget about DNS related issues. Alex On Thu, Apr 30, 2015 at 9:05 AM, Praveen Baratam <praveen.bara...@gmail.com> wrote: > Just to clarify... I was referring to... > > Is it legal to bind Riak to a hostname instead of IP? > > > Yes, it's legal but it will incur the overhead of the lookup. If you're > talking about the HTTP/PBC interfaces, it's best to use IP addresses, but > for the node name, it's totally fine to use a hostname. > Will it be a significant overhead? I believe the it will just be a > function call after the initial lookup rather than a network call. > > Praveen > ᐧ > > On Wed, Apr 29, 2015 at 12:40 AM, Praveen Baratam < > praveen.bara...@gmail.com> wrote: > >> Hello All, >> >> I found it on the FAQ that using hostnames instead of IP addresses will >> incur a overhead! Will it be a significant overhead? I believe that if a >> hostname is queried during startup, the same will be used through the life >> of the VM or in an optimized case till the DNS TTL expires!! >> >> Best, >> >> Praveen Baratam >> >> about.me <http://about.me/praveen.baratam> >> ᐧ >> > > > > -- > Dr. Praveen Baratam > > about.me <http://about.me/praveen.baratam> > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
