#vcloud

© V.CLOUD

© V.cloud | please do not edit

© V.cloud

© V.cloud

© V.cloud | please do not edit

Having a relatively large vcd  setup that services few thousand VMs now, our cell has production load. It seems though that DB connection pooling is not really well handled in the application. Thus,  one could get  connection pool exhaustion. Errors like these in the UI are one of the indications: [ 2c6d3e1e-8fa5-4f4f-859b-96781df7507b ] Cannot open connection - [pool-jetty-12388] Timeout: Pool empty. Unable to fetch a connection in 20 seconds, none available[size:75; busy:75; idle:0; lastwait:20000] One could easily check that is indeed the case: [root@vcd2 ~]# netstat -punta | grep :5432 | wc -l 76 Now, it turns out the vCD appliance also introduces some tune-ups on the postgres DB - namely setting an appropriate value for idle_in_transaction_session_timeout  By default on Centos postgres 10 package from the official postgres rpm repo, this is set to 0 - which means  there is no timeout for long-running transactions. Best practice would  be to handle these in the app. However, vCD  requires a value of 1 hour in the config.  Either apply it run-tme: ALTER DATABASE vcloud SET idle_in_transaction_session_timeout = 3600000; or in postgresql.config file: idle_in_transaction_session_timeout = 3600000   # in milliseconds, 0 is disabled

Ehh ... Ada komputer ukurannya segini teman-teman.. daya listriknya juga cuma 5 Watt Lo ??????? Waaah.... Bisa bayangin ga tuh kalau lab di sekolah kita pakai Vcloudpoint ini, bisa hemat biaya berapa ya ..???????🤔🤔🤔🤔🤔🤔 #vcloud #vcloudpoints100 #vcloudpoint #vcloudpointindonesia #ayohematenergi #hematlistrik #indonesiahematenergi #komputer (di Prima Digital Solusindo) https://www.instagram.com/p/CEDrym0Bw02/?igshid=vgfjbh0i1rsl

https://blogs.vmware.com/vcloud/2019/03/the-hybrid-cloud-gets-better-meet-vcloud-director-9-7.html