[GENIUS-81] opendaylight is consuming too much CPU resource Created: 29/May/17  Updated: 10/May/18  Resolved: 10/May/18

Status: Resolved
Project: genius
Component/s: General
Affects Version/s: Carbon
Fix Version/s: None

Type: Bug
Reporter: yong sheng gong Assignee: Faseela K
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Mac OS
Platform: All


External issue ID: 8556

 Description   

release: carbon/stable release
configuration:
GONGYSH-3:distribution-karaf-0.6.0-Carbon yongshenggong$ cat etc/opendaylight/datastore/initial/config/netvirt-aclservice-config.xml
<aclservice-config xmlns="urn:opendaylight:netvirt:aclservice-config">
<security-group-mode>stateful</security-group-mode>
<default-behavior>deny</default-behavior>
</aclservice-config>

OVS: 2.6.1

transparent seemingly does not have this problem

2017-05-29 12:45:02,457 | INFO | eChangeHandler-0 | LockListener | 344 - org.opendaylight.genius.lockmanager-impl - 0.2.0.Carbon | Received add for lock interfacestun50d944cb5fe : Lock{getLockName=interfacestun50d944cb5fe, getLockOwner=ForkJoinPool-1-worker-1, augmentations={}}
2017-05-29 12:45:02,457 | INFO | eChangeHandler-0 | LockListener | 344 - org.opendaylight.genius.lockmanager-impl - 0.2.0.Carbon | Received remove for lock interfacestun50d944cb5fe : Lock{getLockName=interfacestun50d944cb5fe, getLockOwner=ForkJoinPool-1-worker-1, augmentations={}}
2017-05-29 12:45:02,458 | INFO | nPool-1-worker-1 | IfmUtil | 351 - org.opendaylight.genius.interfacemanager-impl - 0.2.0.Carbon | Binding Service default.tun50d944cb5fe for : tun50d944cb5fe
2017-05-29 12:45:02,458 | INFO | nPool-1-worker-1 | OvsInterfaceStateAddHelper | 351 - org.opendaylight.genius.interfacemanager-impl - 0.2.0.Carbon | Adding Interface State to Oper DS for interface: tun50d944cb5fe
2017-05-29 12:45:02,458 | INFO | eChangeHandler-0 | LockListener | 344 - org.opendaylight.genius.lockmanager-impl - 0.2.0.Carbon | Received add for lock interfacestun50d944cb5fe : Lock{getLockName=interfacestun50d944cb5fe, getLockOwner=ForkJoinPool-1-worker-1, augmentations={}}
2017-05-29 12:45:02,458 | INFO | eChangeHandler-0 | LockListener | 344 - org.opendaylight.genius.lockmanager-impl - 0.2.0.Carbon | Received remove for lock interfacestun50d944cb5fe : Lock{getLockName=interfacestun50d944cb5fe, getLockOwner=ForkJoinPool-1-worker-1, augmentations={}}
2017-05-29 12:45:02,458 | INFO | nPool-1-worker-1 | IfmUtil | 351 - org.opendaylight.genius.interfacemanager-impl - 0.2.0.Carbon | Binding Service default.tun50d944cb5fe for : tun50d944cb5fe
2017-05-29 12:45:02,459 | INFO | nPool-1-worker-1 | OvsInterfaceStateAddHelper | 351 - org.opendaylight.genius.interfacemanager-impl - 0.2.0.Carbon | Adding Interface State to Oper DS for interface: tun50d944cb5fe
2017-05-29 12:45:02,459 | INFO | eChangeHandler-0 | LockListener | 344 - org.opendaylight.genius.lockmanager-impl - 0.2.0.Carbon | Received add for lock interfacestun50d944cb5fe : Lock{getLockName=interfacestun50d944cb5fe, getLockOwner=ForkJoinPool-1-worker-1, augmentations={}}
2017-05-29 12:45:02,459 | INFO | eChangeHandler-0 | LockListener | 344 - org.opendaylight.genius.lockmanager-impl - 0.2.0.Carbon | Received remove for lock interfacestun50d944cb5fe : Lock{getLockName=interfacestun50d944cb5fe, getLockOwner=ForkJoinPool-1-worker-1, augmentations={}}
2017-05-29 12:45:02,459 | INFO | nPool-1-worker-1 | IfmUtil | 351 - org.opendaylight.genius.interfacemanager-impl - 0.2.0.Carbon | Binding Service default.tun50d944cb5fe for : tun50d944cb5fe
2017-05-29 12:45:02,460 | INFO | nPool-1-worker-1 | OvsInterfaceStateAddHelper | 351 - org.opendaylight.genius.interfacemanager-impl - 0.2.0.Carbon | Adding Interface State to Oper DS for interface: tun50d944cb5fe
2017-05-29 12:45:02,460 | INFO | eChangeHandler-0 | LockListener | 344 - org.opendaylight.genius.lockmanager-impl - 0.2.0.Carbon | Received add for lock interfacestun50d944cb5fe : Lock{getLockName=interfacestun50d944cb5fe, getLockOwner=ForkJoinPool-1-worker-1, augmentations={}}
2017-05-29 12:45:02,460 | INFO | eChangeHandler-0 | LockListener | 344 - org.opendaylight.genius.lockmanager-impl - 0.2.0.Carbon | Received remove for lock interfacestun50d944cb5fe : Lock{getLockName=interfacestun50d944cb5fe, getLockOwner=ForkJoinPool-1-worker-1, augmentations={}}
2017-05-29 12:45:02,460 | INFO | nPool-1-worker-1 | IfmUtil | 351 - org.opendaylight.genius.interfacemanager-impl - 0.2.0.Carbon | Binding Service default.tun50d944cb5fe for : tun50d944cb5fe
2017-05-29 12:45:02,460 | INFO | nPool-1-worker-1 | OvsInterfaceStateAddHelper | 351 - org.opendaylight.genius.interfacemanager-impl - 0.2.0.Carbon | Adding Interface State to Oper DS for interface: tun50d944cb5fe
2017-05-29 12:45:02,461 | INFO | eChangeHandler-0 | LockListener | 344 - org.opendaylight.genius.lockmanager-impl - 0.2.0.Carbon | Received add for lock interfacestun50d944cb5fe : Lock{getLockName=interfacestun50d944cb5fe, getLockOwner=ForkJoinPool-1-worker-1, augmentations={}}
2017-05-29 12:45:02,461 | INFO | eChangeHandler-0 | LockListener | 344 - org.opendaylight.genius.lockmanager-impl - 0.2.0.Carbon | Received remove for lock interfacestun50d944cb5fe : Lock{getLockName=interfacestun50d944cb5fe, getLockOwner=ForkJoinPool-1-worker-1, augmentations={}}
2017-05-29 12:45:02,461 | INFO | nPool-1-worker-1 | IfmUtil | 351 - org.opendaylight.genius.interfacemanager-impl - 0.2.0.Carbon | Binding Service default.tun50d944cb5fe for : tun50d944cb5fe
2017-05-29 12:45:02,461 | INFO | nPool-1-worker-1 | OvsInterfaceStateAddHelper | 351 - org.opendaylight.genius.interfacemanager-impl - 0.2.0.Carbon | Adding Interface State to Oper DS for interface: tun50d944cb5fe
2017-05-29 12:45:02,462 | INFO | eChangeHandler-0 | LockListener | 344 - org.opendaylight.genius.lockmanager-impl - 0.2.0.Carbon | Received add for lock interfacestun50d944cb5fe : Lock{getLockName=interfacestun50d944cb5fe, getLockOwner=ForkJoinPool-1-worker-1, augmentations={}}



 Comments   
Comment by Sam Hague [ 10/Jul/17 ]

Moved this over to genius since these logs are genius logs.

Is it possible that is the only issue, that the default logging is at INFO?

Comment by Faseela K [ 08/Aug/17 ]

Hi,

For a production deployment, you are not supposed to run on INFO logs.
Please turn off INFO logs after logging into karaf, and check if you are still seeing high CPU. If so please collect jstack/JFR output on the karaf process, and attach to the TR, we will have a look.

We have fixed some of the high CPU issues in master/carbon recently, so please do check if you see the issue on latest builds.

Thanks,
Faseela

Comment by Michael Vorburger [ 26/Oct/17 ]

This issue does not seem to be actionable to me - we would need Java profiling details.. I would close this.

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