SYMC: Kill Haproxy process does not automatically spawn a new haproxy

I tried manually killing haproxy on hypervisor and see it it spawns a new haproxy somewhere else, but I don't see that happening. The database still points to the old active/standby instances which does not seem to be correct.

[ash2] varun_lodaya@b0d009ash2006:~$
[ash2] varun_lodaya@b0d009ash2006:~$ ps -ef | grep haproxy

nobody 28985 1 0 17:27 ? 00:00:00 haproxy -f /var/lib/contrail/loadbalancer/bbf5cf9a-f643-4a4e-9dd7-038818d5739e/etc/haproxy/haproxy.cfg -D -p /var/lib/contrail/loadbalancer/bbf5cf9a-f643-4a4e-9dd7-038818d5739e/etc/haproxy/haproxy.cfg.pid -sf 28970

[ash2] varun_lodaya@b0d009ash2006:~$ sudo kill -9 28985
[ash2] varun_lodaya@b0d009ash2006:~$

Same virtual_machine_back_refs even after killing haproxy on 1 node.

"virtual_machine_back_refs": [
            {
                "attr": null,
                "href": "http://localhost:9100/virtual-machine/779e583e-2c89-4747-a7ef-c0bf94ce4a8c",
                "to": [
                    "SDN__sdn__64f5f871-4ac9-4e3f-bf41-37f47c380016__1"
                ],
                "uuid": "779e583e-2c89-4747-a7ef-c0bf94ce4a8c"
            },
            {
                "attr": null,
                "href": "http://localhost:9100/virtual-machine/e2ca90ec-9653-4219-a94a-9c02a3584028",
                "to": [
                    "SDN__sdn__64f5f871-4ac9-4e3f-bf41-37f47c380016__2"
                ],
                "uuid": "e2ca90ec-9653-4219-a94a-9c02a3584028"
            }
        ]