[OPNFLWPLUG-227] FRM/Statistics Manager: figure out flow indexing Created: 04/Aug/14  Updated: 27/Sep/21  Resolved: 06/Aug/14

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

Type: Bug
Reporter: Robert Varga Assignee: Vaclav Demcak
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Blocks
blocks CONTROLLER-661 Statistics Manager performance poor f... Resolved
Duplicate
duplicates OPNFLWPLUG-85 Node Status reconciliation between co... Resolved
External issue ID: 1477
Priority: Highest

 Description   

Currently we do not have a way how statistics manager can cross-reference a flow stats report to a preconfigured flow.

This results in org.opendaylight.controller.md.statistics.manager.FlowStatsTracker needing to go through entire configured flow table on each flow statistics report, which simply does not scale.

FRM needs to enforce non-existing cookie, then expose a cookie->FlowKey mapping in datastore. Then SM can lookup the FlowKey based on cookie, and Flow from FlowKey.



 Comments   
Comment by Kamal Rameshan [ 06/Aug/14 ]

There is a gerrit which seem to have similar changes: https://git.opendaylight.org/gerrit/#/c/8174

FlowCookieProducer is created here which i believe does the same as desired to solve this issue.

Comment by Vaclav Demcak [ 06/Aug/14 ]

Partial indexing is a part of:
https://git.opendaylight.org/gerrit/#/c/8174

Index map between "unique" flowCookie and List<flowId> is created in StatisticManager (no in FRM) because you are not be able to ensure unique pair flowCookie->List<flowId> for reconnected device (configured device which lost connection -> disconnection clean FlowCookieMap<flowCookie,List<flowId>> in DataStore/OPERATIONAL)
FRM makes "unique" flowCookie index only for preventing huge efort by identification correct flowId for lager flow suite with same flowCookie in DataStore/CONFIGURATION in same flowNode table. But FRM doesn't need to remeber a pair flowCookie - flowId.

More here:
https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Backlog:Node_Status_Reconciliation

Generated at Wed Feb 07 20:31:54 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.