flow_config_perf.py
[OPNFLWPLUG-283] Logging flow deletions despite log level set to ERROR Created: 18/Sep/14 Updated: 27/Sep/21 Resolved: 23/Oct/14 |
|
| Status: | Resolved |
| Project: | OpenFlowPlugin |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jan Medved | Assignee: | Jan Hajnar |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
flow_config_perf.py
|
| External issue ID: | 1945 |
| Description |
|
The following logs are being logged despite the log level is set to ERROR: 2014-09-17 20:40:11,930 | INFO | qtp103994434-447 | BrokerFacade | 167 - org.opendaylight.controller.sal-rest-connector - 1.1.0.SNAPSHOT | Delete CONFIGURATION via Restconf: /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[ {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:7}]/AugmentationIdentifier {childNames=[(urn:opendaylight:flow:inventory?revision=2013-08-19)manufacturer, (urn:opendaylight:flow:inventory?revision=2013-08-19)hardware, (urn:opendaylight:flow:inventory?revision=2013-08-19)software, (urn:opendaylight:flow:inventory?revision=2013-08-19)serial-number, (urn:opendaylight:flow:inventory?revision=2013-08-19)description, (urn:opendaylight:flow:inventory?revision=2013-08-19)meter, (urn:opendaylight:flow:inventory?revision=2013-08-19)table, (urn:opendaylight:flow:inventory?revision=2013-08-19)group, (urn:opendaylight:flow:inventory?revision=2013-08-19)ip-address, (urn:opendaylight:flow:inventory?revision=2013-08-19)supported-match-types, (urn:opendaylight:flow:inventory?revision=2013-08-19)supported-instructions, (urn:opendaylight:flow:inventory?revision=2013-08-19)supported-actions, (urn:opendaylight:flow:inventory?revision=2013-08-19)switch-features]}/(urn:opendaylight:flow:inventory?revision=2013-08-19)table/table[ {(urn:opendaylight:flow:inventory?revision=2013-08-19)id=0}]/flow/flow[ {(urn:opendaylight:flow:inventory?revision=2013-08-19)id=309999}] According to the log's header (and logic), this log should only appear if the log level is info. To reproduce, set all log levels in logback.xml to ERROR, start teh controller and run the attached performance python script with the following command line: >python flow_config_perf.py --nflows 1000 --nthreads=10 mininet was not connected. This bug is affecting performance. |
| Comments |
| Comment by Jan Medved [ 18/Sep/14 ] |
|
Attachment flow_config_perf.py has been added with description: Flow config script |
| Comment by Tony Tkacik [ 18/Sep/14 ] |
|
How did you modified logging configuration? There are several bug reports |
| Comment by Jan Hajnar [ 18/Sep/14 ] |
|
To my knowledge, karaf does not load log config from logback.xml. It uses Pax Logging service and config file is located in etc/org.ops4j.pax.logging.cfg To change to error level globaly you should change line with "log4j.rootLogger=INFO, out, osgi:" to "log4j.rootLogger=ERROR, out, osgi:" Also you can change level for individual loggers like: maybe we could recreate setup from logback.xml in Pax Logging config file. also logging levels and loggers can be edited through karaf command line wit log:set command: |
| Comment by Ed Warnicke [ 18/Sep/14 ] |
|
http://karaf.apache.org/manual/latest-2.2.x/users-guide/logging-system.html |
| Comment by Ed Warnicke [ 18/Sep/14 ] |
|
Note the correct place for any changes to logging defaults would be here: controller/opendaylight/distribution/opendaylight-karaf-resources/src/main/resources |