[USC-7] Each update of shard data by the manager has a several-second delay Created: 01/Jun/15 Updated: 19/Oct/17 Resolved: 22/Jun/15 |
|
| Status: | Resolved |
| Project: | usc |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Gary Wu | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 3534 |
| Description |
|
Each update to the shard data by the manager has a delay of several seconds. It was found that UscTopologyService.updateShard() was using a non-thread-safe construct to wait for the completion of the async callback. |
| Comments |
| Comment by Gary Wu [ 01/Jun/15 ] |
|
Issue will be fixed by removing the Thread.sleep() loop and using a CountDownLatch instead. |
| Comment by Gary Wu [ 01/Jun/15 ] |
|
Fix proposed in https://git.opendaylight.org/gerrit/#/c/21592/ |
| Comment by A H [ 22/Jun/15 ] |
|
Fix merged in https://git.opendaylight.org/gerrit/#/c/21592/ |