[SERVER-80292] Fail start with error information when connection fails Created: 21/Aug/23 Updated: 29/Oct/23 Resolved: 08/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Normyle | Assignee: | Matthew Normyle |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | init-337-m3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Atlas Streams
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sprint 31 |
| Participants: |
| Description |
|
Also, in this ticket we should handle:
|
| Comments |
| Comment by Sandeep Dhoot [ 28/Aug/23 ] |
|
Agreed, will send a slack message for it. |
| Comment by Matthew Normyle [ 28/Aug/23 ] |
|
sandeep.dhoot@mongodb.com we should bring this up with the team. Pretty sure product expects that a Start call will fail when the connection fails. I doubt it's a private preview blocker though. |
| Comment by Sandeep Dhoot [ 26/Aug/23 ] |
|
Instead of failing start() I am thinking of letting the stream processor run and returning error/not-connected status in the response of listStreamprocessors. |