[OVSDB-368] no retry mechanism for mdsal read or write failures Created: 30/Aug/16  Updated: 01/May/19

Status: Open
Project: ovsdb
Component/s: Southbound.hw_vtep
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: suneel verma 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: 6578

 Description   

before pushing the config updates to device, it does a read of operational datastore.
if the read of operational datastore fails there is no retry mechanism.

Same goes with the processing of updates from the device.
if the write to operational datastore no retry is inplace.

Not sure if the OVSDB-338 also is about the same.

 Comments   
Comment by Anil Vishnoi [ 02/Feb/17 ]

Hi Vishal,

Are you planning to work on this enhancement? Otherwise we can ask in the community if anybody want to pick it up.

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