# Initial load config loading is timing out

**URL:** https://dmap-community.ductus.global/t/initial-load-config-loading-is-timing-out/402
**Category:** CDB and CDB API
**Created:** [March 2, 2016, 11:17pm UTC](https://dmap-community.ductus.global/t/initial-load-config-loading-is-timing-out/402 "2016-03-02T23:17:46Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![phani](https://avatars.discourse-cdn.com/v4/letter/p/f1d935/32.png) [@phani](https://dmap-community.ductus.global/u/phani)
#### Post date: [March 2, 2016, 11:17pm UTC](https://dmap-community.ductus.global/t/initial-load-config-loading-is-timing-out/402/1 "2016-03-02T23:17:46Z")

</div>

Hi,  
During loading of initial config , time out is happening . Currently we have increased cdb\_set\_timeout. Is there any other mechanism available , to inform confd that, did not time out and still processing the config. (kind of keep alive mechanism )

Thanks  
Phani

---

<div class="post-metadata">

### Author: ![waitai](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/waitai/32/436_2.png) [@waitai](https://dmap-community.ductus.global/u/waitai)
#### Post date: [March 3, 2016, 12:28am UTC](https://dmap-community.ductus.global/t/initial-load-config-loading-is-timing-out/402/2 "2016-03-03T00:28:16Z")

</div>

Have you tried setting the cdb’s clientTimeout value to infinity in confd.conf? With that setting, CDB will never timeout waiting for a response from a client.

You can also refer to this [cdb-client-tmeout-interval related posting](https://discuss.tail-f.com/t/is-there-a-way-to-control-the-cdb-client-timeout-interval/131?u=waitai) for more information.