[CONTROLLER-273] high CPU on ODL startup Created: 03/Apr/14  Updated: 25/Jul/23  Resolved: 24/Apr/14

Status: Resolved
Project: controller
Component/s: config
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Giles Heron Assignee: Tomas Olvecky
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC

Attachments: Zip Archive opendaylight2.zip    
External issue ID: 659

 Description   

When starting ODL it seems to consume all available CPU - for anywhere upwards of 20 CPU minutes (I'm testing on a quad CPU system). If I increase controller logging to debug then the CPU seems to get soaked indefinitely (I gave up after about 90 minutes of CPU time - ODL still hadn't finished startup).

Once ODL finishes startup (NETCONF is up to my 4 routers and BGP-LS is up to the one BGP-LS speaker) then CPU returns to a normal level.

I'm wondering if this issue was introduced by the change from configuration over netconf to direct use of Java APIs (I'm pretty sure I didn't see it before that change).

logs for the case with controller logging set to INFO showed that it took just over 5 minutes to get to the end of the configuration persister.

attached (and zipped) logs for the case where controller logging was set to DEBUG show that after 9 or 10 minutes we run out of heap space and there were no more logs. MAVEN_OPTS was set to "-Xmx1024m -XX:MaxPermSize=512m".

 Comments   
Comment by Giles Heron [ 03/Apr/14 ]

Attachment opendaylight2.zip has been added with description: zipped log-file showing out of heap space on startup with -Xmx1024m

Comment by Tomas Olvecky [ 24/Apr/14 ]

Hi,
from the log file I don't see what the issue might be. Only the OOM: MAVEN_OPTS only affect maven build, so please use run.sh -Xmx2G
If the issue still persists, can you give me a pointer where to the environment?

Comment by Giles Heron [ 24/Apr/14 ]

Hi Tomas,

I think this one is fixed now we've moved to 2G of heap memory.

and yes - my mistake re the MAVEN_OPTS. I figured that one out eventually

Giles

Generated at Wed Feb 07 19:52:37 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.