[CONTROLLER-1721] binding-broker-impl occasionally takes too long to finish Created: 13/Jun/17 Updated: 25/Jul/23 Resolved: 05/Oct/18 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | blueprint |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 8678 |
| Description |
|
Seen once so far, in Netconf This is very similar to AAA-132 but different config subsystem capability is taking too long this time: did not finish after 74969 ms Leading to clustering failure: |
| Comments |
| Comment by Robert Varga [ 24/Aug/17 ] |
|
This is probably caused by blueprint service start ordering. |
| Comment by Tom Pantelis [ 15/Sep/17 ] |
|
The DeadlockMonitor warn does not lead to the clustering error. In fact it's the other way around. CDS waits up to 90s for all shard to elect leaders which blocks all other dependent blueprint containers from starting, including the binding broker which in turn blocks the CSS "binding-broker-impl" module from completing startup, hence the DeadlockMonitor warning. As we've seen in other cases, it seems test environment load can delay startup and node connectivity. |