High CPU utilisation of woker container. #186

Activity

1. hanefi commented on Apr 13, 2020

   

   Hanefi Onaldi (hanefi)

   on Apr 13, 2020

   Last edited by hanefi

   Contributor

   More actions

   Thanks Ankur Mahajan (@mahajanankur) for reporting this.

   I created two PRs that aims to resolve this issue:
   1. citusdata/membership-manager#9 implements a polling mechanism in Membership Manager, so that (a) it will detect the readiness of the coordinator node, (b) properly report that it is ready to accept new Citus worker services

   2. #187 (a) updates the docker images to properly detect dependencies, (b) introduce Compose V3 definitions

   Once they are merged, this issue should be resolved

   Edit: this issue seems unrelated to my fixes
2. mahajanankur commented on Apr 13, 2020

   

   Ankur Mahajan (mahajanankur)

   on Apr 13, 2020

   Last edited by mahajanankur

   Author

   More actions

   Hanefi Onaldi (@hanefi), just to inform you, the issue is still there even after shutting down the membership-manager container.
   Server with load
   

   Idle server
   

   Update:
   The Citus docker ecosystem pooling the data frequently due to which CPU and I/O gets chocked. This happens even if there is no load or even no schema.
3. Ankur Mahajan (mahajanankur)

   changed the title [-]High CPU utilisation due to membership-manager docker.[/-] [+]High CPU utilisation of wokers due to membership-manager docker.[/+] on Apr 14, 2020
4. Ankur Mahajan (mahajanankur)

   changed the title [-]High CPU utilisation of wokers due to membership-manager docker.[/-] [+]High CPU utilisation of woker container.[/+] on Apr 14, 2020