[YANGTOOLS-272] support needed from md-sal infra to safely remove common portion of instanceId when all leaf users are removed Created: 19/Aug/14 Updated: 10/Apr/22 Resolved: 04/Feb/15 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Flavio Fernandes | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||||||
| Description |
|
In the process of moving from deprecated DataBrokerService to the new DataBroker, many implementations began using the 'createParents=true' param; to That behavior is handy but may now be generating a potential leak (aka obsolete reference) when all users of the 'shared' part of the tree are done using it. For the implementations, it would not be proper to remove from the 'root' as it could potentially delete other configuration data that is hanging off the same tree; so the best it can do is to remove it's 'authoritative' portion. Ref link: https://gist.github.com/864043e0a96c4e704497 |
| Comments |
| Comment by Ed Warnicke [ 19/Aug/14 ] |
|
This is actually an interesting problem: With multiple writers sharing a tree (like node) how do we determine when For some use cases (like an operational node with a single authoritative writer) this is doable (see the case of openflow nodes in the operational tree when they disconnect). But its not clear what to do in general, and needs to be figured out. 'Last one to leave turns out the light' may provide to be a useful tool in the tool box for many uses cases. |