[ODLPARENT-115] Karaf is slow to start processing features after start Created: 14/Sep/17 Updated: 24/Jan/18 Resolved: 09/Oct/17 |
|
| Status: | Verified |
| Project: | odlparent |
| Component/s: | General |
| Affects Version/s: | 2.0.5 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 9161 | ||||||||
| Description |
|
This was first reported as a comment [0] to Compared to Carbon (Karaf 3), Nitrogen (Karaf 4) Distribution takes much longer to start. Probably the cause is the new way of generating features from pom files, and inefficient algorithm used when parsing feature repositories present in Distribution. An example is karaf.log [2] showing it took 4 minutes to parse feature repositories even though no odl feature was being installed at that time (only standard and wrap features): While this is just a performance regression, this has required a workaround [1] in distribution offline test job, and in the future this might also limit size of features able to finish SingleFeatureTest in time. As this is probably a bug inherited from Karaf project, version upgrade will be needed to fix this. [0] https://bugs.opendaylight.org/show_bug.cgi?id=8258#c3 |
| Comments |
| Comment by Robert Varga [ 14/Sep/17 ] |
|
The problem is upstream. We need a 4.0.10 karaf release and integrate it. The following PR brings down the bood time from 102 to <3 seconds in my testing: |
| Comment by Robert Varga [ 25/Sep/17 ] |
| Comment by Robert Varga [ 28/Sep/17 ] |
|
Fixed in 2.0.5 |
| Comment by Vratko Polak [ 09/Oct/17 ] |
|
According to offline job console [5], Nitrogen now takes 19 seconds to start without ODL features and 61 seconds to install odl-integration-all. |