syncgateway replicate target DNS resolution

[arihant rk]

I am using below replication config in the replication. On the destination side i have 2 sg-replicate nodes with fqdn at source to resolve. but could see that always requesting are hitting to only one sg-replicate.

I could see that every time http request is normal. DNS resolution is resolving to list of ips in random manner.

"replications":[

   {

               "replication_id":"C1_C2",

               "source": "db",

               "target": "http://prod-GWREP-V1.service.2.com:4985/db/",

               "continuous":true,

               "changes_feed_limit":1000

    }],

is there caching happening at the start of sg-replicate, if so what is the need of everytime DNS resolution.

[Traun Leyden]

We're not doing anything special in the sg-replicate code with respect to dns lookups (on purpose), so I think it's probably a lower level issue.  

It might be a problem with your DNS server configuration, or an issue with the go http library.

Just to clarify actual vs expected though, are you saying you are seeing more DNS lookups than expected?  What's the TTL set to on your DNS entries?

--
You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobile-couchbase+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/a94efbdb-da8b-468c-a610-dfa1dbe036db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[arihant rk]

TTL is 10 seconds, we are seeing DNS looksup but not able correlate at which point DNS lookup is happening. what is the go version in syncgateway 1.3.1.  cpuld able to syncgateway replicator is not making long poll conection.

are each of request syncgateway replicator does DNS lookup before start of replication(batch between GET and PUT of local document)

[Traun Leyden]

10 second TTL seems like it's pretty short, I wouldn't be surprised if it's causing some of your issues:

http://serverfault.com/questions/7478/recommended-dns-ttl

According to this, SG 1.3 was built with Go 1.5: 

https://github.com/couchbase/sync_gateway/tree/1.3#build-pre-requisites

--

You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobile-couchbase+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/bb096a8c-935b-42ef-801f-cbf73f8ad262%40googlegroups.com.

[arihant rk]

The setting we have set for testing purpose. I am more worried about why sg-replicate is not load balancing the requests even-though DNS resolving to different IP's.

On Thursday, January 12, 2017 at 11:15:37 PM UTC+5:30, Traun Leyden wrote:

10 second TTL seems like it's pretty short, I wouldn't be surprised if it's causing some of your issues:

http://serverfault.com/questions/7478/recommended-dns-ttl

According to this, SG 1.3 was built with Go 1.5: 

https://github.com/couchbase/sync_gateway/tree/1.3#build-pre-requisites

On Thu, Jan 12, 2017 at 2:08 AM, arihant rk <ark...@gmail.com> wrote:

TTL is 10 seconds, we are seeing DNS looksup but not able correlate at which point DNS lookup is happening. what is the go version in syncgateway 1.3.1.  cpuld able to syncgateway replicator is not making long poll conection.

are each of request syncgateway replicator does DNS lookup before start of replication(batch between GET and PUT of local document)

On Thursday, January 12, 2017 at 12:15:07 PM UTC+5:30, arihant rk wrote:

I am using below replication config in the replication. On the destination side i have 2 sg-replicate nodes with fqdn at source to resolve. but could see that always requesting are hitting to only one sg-replicate.

I could see that every time http request is normal. DNS resolution is resolving to list of ips in random manner.

"replications":[

   {

               "replication_id":"C1_C2",

               "source": "db",

               "target": "http://prod-GWREP-V1.service.2.com:4985/db/",

               "continuous":true,

               "changes_feed_limit":1000

    }],

is there caching happening at the start of sg-replicate, if so what is the need of everytime DNS resolution.

--
You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mobile-couchba...@googlegroups.com.