[CONTROLLER-1739] Dsbenchmark: Conflicting modification for test-status on install Created: 10/Jul/17  Updated: 25/Jul/23

Status: Open
Project: controller
Component/s: clustering
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Vratko Polak 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:
Duplicate
is duplicated by CONTROLLER-1552 odl-mdsal-benchmark does not wait for... Resolved
External issue ID: 8829

 Description   

This is very similar to CONTROLLER-1552 but the transaction failure cause is different, so opening a new bug.

Benchmark is not a Bugzilla component for Controller project, so opening under Clustering component.

Upon installation of odl-mdsal-benchmark, each member tries to write initial test-status transaction. In very rare cases, two members submit at the same time, leading to "ConflictingModificationAppliedException: Node was created by other transaction".

As this is happening in config-pusher, unhandled OptimisticLockFailedException prevents creation of ModuleIdentifier

{factoryName='dsbenchmark-impl', instanceName='dsbenchmark-default'}

which leads to "Configuration Transaction failed on 2PC, server is unhealthy" and a red dot in CSIT. See job console output [0].

[0] https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-periodic-benchmark-only-carbon/322/console.log.gz

 Comments   
Comment by Vratko Polak [ 10/Jul/17 ]

Temporary Carbon workaround [1] similar to NETCONF-346 fix. Let the error happen, but catch it and log warning.

[1] https://git.opendaylight.org/gerrit/52317

Comment by Vratko Polak [ 10/Jul/17 ]

Correction: [2] is for Carbon.
[1] is for Nitrogen (and fails perhaps because of ongoing Karaf 4 migration).

[2] https://git.opendaylight.org/gerrit/60141

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