[MGNLPER-30] Lifecycle hooks for suppliers to handle resources correctly Created: 08/May/18 Updated: 06/Feb/19 Resolved: 23/Jan/19 |
|
| Status: | Closed |
| Project: | Periscope |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1 |
| Type: | Task | Priority: | Minor |
| Reporter: | Michael Mühlebach | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Epic Link: | Periscope improvements |
| Description |
|
{{SearchResultSupplier}}s can have external resources like rest connections or executors/queues etc. Those should not be created in the constructor and should be shutdown and/or stop correctly as well. The SearchResultSupplier should provide hooks for those lifecycle events do manage resources correctly. Additionally external resources, especially when the network is involved, can become unavailable for a short period of time or be not available at startup. Suppliers should deal with those scenarios gracefully and should certainly not require a restart. |