Description of problem:
Adding a goroutine for each event either from libovsdb cache or from ovnkube-master informer handler may cause golang needless pressure for go runtime to spawn so many go routines.

Version-Release number of selected component (if applicable):


How reproducible:
Unknown. Youd have to create a large amount of events. It was seen once during runtime that libovsdb cache was dropping events and we suspect it was due to the metrics handler. We could not prove for sure that this was the case however.

Steps to Reproduce:
1. Create a very large amount of events from OVN
2. Libovsdb cache will log that it is dropping events due to queue full


Actual results:


Expected results:


Additional info: