Comment 3 for bug 1782314

The impact reported by a customer who has hit the issue:

All the Services implemented in Openstack and the OpenDaylight SDN controller enforce tenant isolation in the dataplane for all the tenants. However, in the control plane common models/tables are used which hold all the different tenant information together. Now that said, in SDN-based deployments that run Openstack Mitaka, even if single row in Neutron DB is corrupted, it has the potential to
affect all the future orchestrations not just for that tenant, but for all the existing / new tenants. This is a limitation with the Mitaka version of the Openstack OpenDaylight V1 Driver of Neutron community.

Due to the corrupted rows in the table causing ODL Neutron V1 Driver to continuously thrash the system thereby making it consume more memory as well as taking away lot of CPU cycles .