[BGPCEP-388] Documentation on how to change PCEP config for 3-node cluster is needed Created: 04/Feb/16  Updated: 03/Mar/19  Resolved: 09/Feb/16

Status: Resolved
Project: bgpcep
Component/s: PCEP
Affects Version/s: Bugzilla Migration
Fix Version/s: Bugzilla Migration

Type: Bug
Reporter: Vratko Polak Assignee: Milos Fabian
Resolution: Done 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: 5235

 Description   

Running Beryllium cluster with odl-integration-compatible-with-all installed on all nodes, there is possibility a node will end up in "server is unhealthy". Search for "resource-denied" in [0] and read onwards.

If this is not a Bug in PCEP code, it means 39-pcep-provider.xml contains data not suitable for cluster deployment. We (releng/builder or integration/test) can prepare different content for this file on each node, but we need a documentation from Bgpcep project, preferable as a wiki page.

This is beginning of the first exception in log:

2016-02-03 01:31:56,371 | WARN | lt-dispatcher-32 | ConcurrentDOMDataBroker | 143 - org.opendaylight.controller.sal-distributed-datastore - 1.3.0.SNAPSHOT | Tx: DOM-0 Error during phase CAN_COMMIT, starting Abort
OptimisticLockFailedException

{message=Optimistic lock failed., errorList=[RpcError [message=Optimistic lock failed., severity=ERROR, errorType=APPLICATION, tag=resource-denied, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was created by other transaction.]]}

at org.opendaylight.controller.cluster.datastore.SimpleShardDataTreeCohort.canCommit(SimpleShardDataTreeCohort.java:54)

[0] https://jenkins.opendaylight.org/releng/view/controller/job/controller-csit-3node-clustering-all-beryllium/108/consoleFull

 Comments   
Comment by Milos Fabian [ 08/Feb/16 ]

BGP: https://wiki.opendaylight.org/view/BGP_LS_PCEP:User_Guide#3-node_Clustering

BMP: https://wiki.opendaylight.org/view/BGP_LS_PCEP:User_Guide#3-node_Clustering_3

PCEP: https://wiki.opendaylight.org/view/BGP_LS_PCEP:User_Guide#3-node_Clustering_2

Comment by Vratko Polak [ 09/Feb/16 ]

Looks good. But perhaps data change counter also needs a few comments about usage in 3-node cluster.

Comment by Milos Fabian [ 09/Feb/16 ]

(In reply to Vratko Polák from comment #2)
> Looks good. But perhaps data change counter also needs a few comments about
> usage in 3-node cluster.

Right, I forgot about it. In current state, data-change-counter is not able to work in 3-node cluster deployment with enabled replication, as singleton instance can be created only. This will require some modifications (API change as well as) - opening a new bug.

Comment by Milos Fabian [ 09/Feb/16 ]

Data Change Counter: https://wiki.opendaylight.org/view/BGP_LS_PCEP:Testing_components#3-node_Clustering

Generated at Wed Feb 07 19:12:54 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.