[MDSAL-274] Singleton Clustering : No way for non-candidate to check if ServiceInstance in other member is active Created: 13/Jul/17  Updated: 09/Jan/24

Status: Open
Project: mdsal
Component/s: CSS, EOS
Affects Version/s: None
Fix Version/s: 14.0.0

Type: Bug
Reporter: Anil Vishnoi Assignee: Unassigned
Resolution: Unresolved 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 OPNFLWPLUG-1072 ContextChainHolderImpl encroaches on ... Confirmed
External issue ID: 8855

 Description   

When openflow plugin device connect to all the three controllers in cluster, instance for which instantiateServiceInstance() is called will send the MASTER role request to the device. But there is no way for other two instances to know when to send the SLAVE role, because closeServiceInstance() won't be call for those and that make sense looking at the purpose of the API. Also there is no API for candidates to enquire if is there any existing instance that is active for the register service entity, so it can assume that it's a non-active/non-owner instance and it can send the slave role to the device. In the current implementation of openflowplugin we are using timeout task to check if the the service entity is owner or not, and in my opinion it's very bad approach. I think Singleton service should either provide an API to enquire the ownership status of the service entity or it should call the closeServiceInstance() if it's not an active instance.


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