Kong fails to create balancer for service

Hi all,

I’m running some tests on Kong v. 1.3.0 dbless with Kong Ingress Controller 0.5.0, and I’m running into this issue:

2019/09/10 00:06:55 [error] 39#0: *9410 [lua] balancer.lua:581: get_balancer(): balancer not found for test-service.default.svc, will create it, client: 172.17.0.1, server: kong, request: "GET /test-service HTTP/1.1", host: ""
2019/09/10 00:06:56 [crit] 39#0: *2612 [lua] balancer.lua:642: on_upstream_event(): failed creating balancer for test-service.default.svc: timeout waiting for balancer for cce2a580-fb43-59e4-a015-4f46553062d6, client: 172.17.0.1, server: kong, request: "GET /test-service HTTP/1.1", host: ""
2019/09/10 00:07:15 [error] 39#0: *13755 [lua] balancer.lua:581: get_balancer(): balancer not found for test-service.default.svc, will create it, client: 172.17.0.1, server: kong, request: "GET /test-service HTTP/1.1", host: ""
2019/09/10 00:07:26 [crit] 39#0: *2612 [lua] balancer.lua:642: on_upstream_event(): failed creating balancer for test-service.default.svc: timeout waiting for balancer for cce2a580-fb43-59e4-a015-4f46553062d6, client: 172.17.0.1, server: kong, request: "GET /test-service HTTP/1.1", host: ""

Let me know if there is anything else you need.

Thanks,
Arnav

Never mind, issue appears to be resolved by giving Kong more memory to work with.

@ArnavB I am also facing same issue, how much memory you have allocated to proxy and ingress controller containers ?

@Pankaj_Kumar, I’m sorry I no longer have access to this project, and I do not remember the configuration. If you really need to, you can set extremely high memory values for both and then troubleshoot from there.

Cool thanks, I will try it out.