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
Problem
We are using LogNet/grpc-spring-boot-starter, which is defining the grpcInternalConfigurator Consumer along with spring-cloud-stream.
We are using spring-cloud-stream for creating binding for use with StreamBridge 1. And do not have any functions.
In the absense of spring.cloud.function.definition= property, the consumer defined by lognet is picked up and default binding is created, and repeatedly tries to bind it to while trying to create stream [grpcInternalConfigurator-in-0], while spring.cloud.stream.kinesis.binder.autoCreateStream=false.
This causes an very verbose error message few times every second, which is inundating out cloudwatch log stream, adding to cost.
org.springframework.cloud.stream.provisioning.ProvisioningException: The stream [grpcInternalConfigurator-in-0] was not found and auto creation is disabled.; nested exception is com.amazonaws.services.kinesis.model.ResourceNotFoundException
Solution
Stream binding (autoconfiguration) on autoscan of beans be limited only at startup.
Alternative considered
None that is acceptable:
create a stream [grpcInternalConfigurator-in-0]
define dummy supplier functions and add a stream binding for it.