[SXP-145] Configuration class clustering problems Created: 14/Sep/18  Updated: 12/Nov/18  Resolved: 12/Nov/18

Status: Resolved
Project: sxp
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Ivan Hrasko Assignee: Ivan Hrasko
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: SXP Clustering bugs

 Description   

Configuration class holds a map of SXP nodes which is inefficient in cluster environment:

      1. It is not possible to add node and verify that node is added to configuration.

      2. It is not possible to invoke some RPC operations which delas with SXP nodes on other that cluster owner node.

 

Configuration is not shared across all cluster nodes. It is probably only on cluster owner.

Consequences:

When adding SXP node on other than owner cluster node it is not possible to verify that node is added to Configuration.

When Adding bindings on other than cluster owner node it is not possible to retrieve node and its domain from Configuration (null-pointer).

 

Configuration class should hold only constant configuration.

Probably is used as some kind of cache outside of sxp-core module. It must be improved or removed if it is not possible.



 Comments   
Comment by Ivan Hrasko [ 05/Nov/18 ]

SXP can hold active SXP nodes only on cluster owner thus all operations must be executed only on cluster owner.

Solved by: https://git.opendaylight.org/gerrit/#/c/77079/ and tested by: https://git.opendaylight.org/gerrit/#/c/77256/

For better readability and maintenance: https://git.opendaylight.org/gerrit/#/c/77024/

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