-
Bug
-
Resolution: Duplicate
-
None
-
Carbon
-
None
-
Operating System: All
Platform: All
-
9063
-
Highest
Description of problem: On running longevity tests in a clustered ODL setup we see that one of the ODL instances seems to be up and running as reported by ps output, systemctl and netstat listening ports, however it doesn't seem to be functional. We could not even ssh into the karaf terminal using ssh -p 8101 karaf@172.16.0.16 until we restarted opendaylight. On performing a service restart we were able to get into the karaf shell and ODL seemed to come back up.
Out of the other two instances of ODL, one was killed due to OOM and the other seemed to be running fine. This happens after about 42 hours of running the tests.
Setup:
3 ODLs
3 OpenStack Controllers
3 Compute nodes
Test:
Create 40 neutron resources (rotuers, networks etc) 2 at a time using Rally and delete them over and over again. This is a long running low stress test.
Entire Karaf Log: http://8.43.86.1:8088/smalleni/karaf-controller-0.log.tar.gz
ODL RPM from upstream: python-networking-odl-11.0.0-0.20170806093629.2e78dca.el7ost.noarch
- duplicates
-
CONTROLLER-1756 OOM due to huge Map in ShardDataTree
- Resolved
- is blocked by
-
CONTROLLER-1755 RaftActor lastApplied index moves backwards
- Resolved