[SERVER-85579] Cannot create SP with same name after dropping it Created: 23/Jan/24  Updated: 23/Jan/24

Status: Needs Scheduling
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mayuresh Kulkarni Assignee: Backlog - Atlas Streams
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-85624 Check more often for sink errors Closed
Assigned Teams:
Atlas Streams
Operating System: ALL
Participants:

 Description   

In dev, running into a situation where after dropping a stream processor, a new one with the same name is not being created:

AtlasStreamProcessing> sp.createStreamProcessor("mk-largememtest-1", pipeline)
MongoServerError: Failed to create stream processor: (InvalidOptions) streamProcessor name already exists: mk-largememtest-1: (InvalidOptions) streamProcessor name already exists: mk-largememtest-1, correlationID = 17ace57d05589d7a159978a7
AtlasStreamProcessing> sp["mk-largememtest-1"].drop()
MongoServerError: Failed to drop stream processor: stream processor doesn't exist: stream processor doesn't exist, correlationID = 17ace5806cc5f09815997948
AtlasStreamProcessing> sp.createStreamProcessor("mk-largememtest-1", pipeline)
MongoServerError: Failed to create stream processor: (InvalidOptions) streamProcessor name already exists: mk-largememtest-1: (InvalidOptions) streamProcessor name already exists: mk-largememtest-1, correlationID = 17ace582dbe9439015997991


Generated at Thu Feb 08 06:58:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.