[CONTROLLER-2038] Read transaction does not return full data for the root node Created: 07/Apr/22 Updated: 09/Apr/22 Resolved: 09/Apr/22 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | 5.0.1 |
| Fix Version/s: | 4.0.11, 5.0.2 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Sangwook Ha | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Read transaction on the MD-SAL distributed datastore does not return the full data for the root node. For example, the following code domDataBroker.newReadOnlyTransaction()
.read(LogicalDatastoreType.CONFIGURATION, YangInstanceIdentifier.empty()).get()
only returns partial configuration data. ClientBackedReadTransaction used for ClientBackedDataStore, selected for the tell-based protocol, does not gather data from all the shards like TransactionProxy for DistributedDataStore. Instead it returns data in the 'default' shard only. |
| Comments |
| Comment by Sangwook Ha [ 07/Apr/22 ] |
|
This appears to be the root cause of the daexim CSIT test: daexim-csit-1node-basic-only-sulfur/193 |