# Assert in cdb\_set\_namespace
**URL:** https://dmap-community.ductus.global/t/assert-in-cdb-set-namespace/1590
**Category:** CDB and CDB API
**Created:** [October 13, 2017, 10:23am UTC](https://dmap-community.ductus.global/t/assert-in-cdb-set-namespace/1590 "2017-10-13T10:23:27Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@bkannadassan](https://dmap-community.ductus.global/u/bkannadassan)
#### Post date: [October 13, 2017, 10:23am UTC](https://dmap-community.ductus.global/t/assert-in-cdb-set-namespace/1590/1 "2017-10-13T10:23:27Z")
Hi All!
We are getting following crash…
#0 0x00007f045e5e982d in read () from /lib64/libpthread.so.0
#0 0x00007f045e5e982d in read () from /lib64/libpthread.so.0
#1 0x0000000002472e5d in read\_fill ()
#2 0x000000000247563a in term\_read ()
#3 0x0000000002475ae4 in op\_request\_term ()
#4 0x000000000246adc7 in cdb\_set\_namespace ()
this process gets killed via signal, since it has been hanging in set namespace for more than 5 secs. Is their anyways I can set timeout selectively at that instance so that we don’t hit this issue ?.
rgds
Balaji Kamal Kannadassan
---
### Author:  [@cohult](https://dmap-community.ductus.global/u/cohult)
#### Post date: [October 13, 2017, 11:42am UTC](https://dmap-community.ductus.global/t/assert-in-cdb-set-namespace/1590/2 "2017-10-13T11:42:00Z")
Hi,
See:
`int cdb_set_timeout(int sock, int timeout_secs);`
in the confd\_lib\_cdb(3) man pages, and:
`/confdConfig/cdb/clientTimeout`
in the confd.conf(5) man pages.
---
### Author:  [@bkannadassan](https://dmap-community.ductus.global/u/bkannadassan)
#### Post date: [October 18, 2017, 8:57am UTC](https://dmap-community.ductus.global/t/assert-in-cdb-set-namespace/1590/3 "2017-10-18T08:57:41Z")
Thanks Will check the same.