Yong Hon Kuan

Hi @iancooper , may I know if you know about this behavior ? Or did I doing the configuration wrong ?

Hi @iancooper , some updates from me after a round of testing. This behavior seems to be only happen when there is a huge number of messages involved, we are...

Hi @iancooper , the load test we are running 500 req/sec throughput (Api requests that will publish messages to Kafka). So for this reason I tried to set the commitBatchSize...

Hi @iancooper, I've updated Brighter to v9.1.20 to test. Below are the details: Subscriptions: `new KafkaSubscription( new SubscriptionName("user.session.subscription"), channelName: new ChannelName("user.session.channel"), routingKey: new RoutingKey(messageBusConfig.SubscriptionTopics.UserSessionEvents), groupId: "task-service.group", timeoutInMilliseconds: 500, offsetDefault: AutoOffsetReset.Earliest,...

Hi @iancooper, today I've run the tests again with Sync pipeline (isAsync = false), the result is that the consumer is able to keep up with offsets committed to Kafka....

hi @iancooper, may I know if you are still working on this ?

@iancooper , to understand you correctly, currently implementation of the AWSSQS message gateway is that the message producer will only send messages to RoutingKey, and we want to allow the...