You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched existing issues, it hasn't been reported yet
Issue description
When attempting to modify the Kafka topic name associated with a serverless trigger in our environment, we encountered a critical issue where the operation fails with an error message indicating that the consumer group ID already exists.
Failing use-case: We are using kafka topic "my-sample-v1" and migrating to "my-sample-v2" while consumer group remains same
Error Message: CREATE_FAILED: ProcessorEventSourceMappingKafkaMySampleTopicv2 (AWS::Lambda::EventSourceMapping) Resource handler returned message: "An event source mapping with event source ("kafka-brokers:port"), selfManagedKafkaEventSourceConfig.consumerGroupId ("MySample-Lambda") already exists. Please update or delete the existing mapping with UUID abcd36ef-g166-k263-11b0-00013f812145 (Service: Lambda, Status Code: 409, Request ID: 12345678-0501-1235-1234-12345690ec0d)" (RequestToken: 12345678-0001-1111-2222-12345690ec0d, HandlerErrorCode: AlreadyExists)
Programming Language: Java 17
Additional Notes:
This problem occurs consistently across multiple attempts and environments, indicating a potential bug in the serverless platform's handling of Kafka trigger topic name change keeping the consumer group same.
We also tried deployment after manually deactivating the the kafka trigger, however seems to be no errors but change is not applied as topic remains same
As a workaround, we tried manually removing the trigger and redeploying with new topic name and it worked.
Are you certain it's a bug?
Is the issue caused by a plugin?
Are you using the latest v3 release?
Is there an existing issue for this?
Issue description
When attempting to modify the Kafka topic name associated with a serverless trigger in our environment, we encountered a critical issue where the operation fails with an error message indicating that the consumer group ID already exists.
Failing use-case: We are using kafka topic "my-sample-v1" and migrating to "my-sample-v2" while consumer group remains same
Error Message:
CREATE_FAILED: ProcessorEventSourceMappingKafkaMySampleTopicv2 (AWS::Lambda::EventSourceMapping) Resource handler returned message: "An event source mapping with event source ("kafka-brokers:port"), selfManagedKafkaEventSourceConfig.consumerGroupId ("MySample-Lambda") already exists. Please update or delete the existing mapping with UUID abcd36ef-g166-k263-11b0-00013f812145 (Service: Lambda, Status Code: 409, Request ID: 12345678-0501-1235-1234-12345690ec0d)" (RequestToken: 12345678-0001-1111-2222-12345690ec0d, HandlerErrorCode: AlreadyExists)
Programming Language: Java 17
Additional Notes:
Service configuration (serverless.yml) content
Command name and used flags
N/A
Command output
Environment information
The text was updated successfully, but these errors were encountered: