[CONTROLLER-1029] Clustering : Killing a PCEP PCC-mock session does not result in the Operational datastore losing the PCEP topology Created: 19/Nov/14 Updated: 25/Jul/23 Resolved: 25/Nov/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | RichardHill | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 2408 |
| Description |
|
I am using a build you provided on 14th Friday Nov for clustering testing. distribution-karaf-0.2.1-Helium-SR1 I’ve deployed a 3 node cluster with
I am creating PCEP sessions using the pcep-pcc-mock tool described here. https://wiki.opendaylight.org/view/BGP_LS_PCEP:Testing_components#pcep-pcc-mock java -jar pcep-pcc-mock-0.3.2-SNAPSHOT-executable.jar --log-level DE --local-address 10.25.2.12 --remote-address 10.25.2.9 This creates 1 pcep session. When I access the REST API at 10.194.126.205:8181/restconf/operational/network-topology:network-topology/topology/pcep-topology-1 I see { , }, } I kill the pcep-pcc-mock tool , “ctlr +C” and restart it, I see no changes after 600 seconds. { , }, } |
| Comments |
| Comment by RichardHill [ 19/Nov/14 ] |
|
Attachment karaf.zip has been added with description: log file |
| Comment by RichardHill [ 19/Nov/14 ] |
|
I meant kill not restart the PCEP-PCC-MOCK |
| Comment by RichardHill [ 20/Nov/14 ] |
|
Not seen on https://jenkins.opendaylight.org/integration/job/integration-master-project-centralized-integration/2759/ Deployed as a 3 node cluster on 10.25.2.9 , 10.25.2.10 , 10.25.2.11
|
| Comment by Moiz Raja [ 20/Nov/14 ] |
|
Note that the system property shard.persistent no longer controls persistence. You need to use the config subsystem to disable persistence. |
| Comment by Moiz Raja [ 25/Nov/14 ] |
|
Other fixes have probably resolved this issue. |