[SXP-128] Race condition may cause deleted-then-added node to fail to start correctly Created: 12/Oct/17  Updated: 19/Feb/18

Status: Open
Project: sxp
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Martin Dindoffer 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

External issue ID: 9279

 Description   

When a node is deleted and added in quick succession, the async processing causes it to fail in number of ways.
===Example===
Example of this is in https://logs.opendaylight.org/releng/jenkins092/sxp-csit-1node-periodic-performance-all-carbon/313/
Here the delete RPC deleted a node, then it was readded in another RPC.
However, when it connected, its channel got destroyed:
[127.0.0.1] Server stopped

 Comments   
Comment by Martin Dindoffer [ 20/Oct/17 ]

Oxygen failure may be observed at:
https://logs.opendaylight.org/releng/jenkins092/sxp-csit-1node-periodic-performance-all-oxygen/22

However, this failure has a little bit different behaviour with some additional exceptions. What probably happened is:
1. Node Delete RPC got called and removed the node from mdsal
2. RetryOpenTimer task got invoked but failed to modify the state, because the node was not in mdsal
3. Node Add RPC got called and created the node
4. Server was stopped as an async result of the Delete RPC

Comment by Martin Dindoffer [ 06/Nov/17 ]

Another Nitrogen failure: https://jenkins.opendaylight.org/releng/job/sxp-csit-1node-periodic-performance-all-nitrogen/202/

Comment by Martin Dindoffer [ 19/Feb/18 ]

Another Carbon occurence: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/sxp-csit-1node-periodic-performance-all-carbon/364/odl1_karaf.log.gz

Comment by Martin Dindoffer [ 19/Feb/18 ]

Another Nitrogen occurence: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/sxp-csit-1node-periodic-performance-all-nitrogen/324/odl1_karaf.log.gz

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