Jose Ignacio Gil Jaldo

[watermill-kafka] - cannot process events concurrently without ACKing the event

8

When using watermill-kafka's subscriber, only one event can be processed at the time, unless you ACK the event. That, disregard the number of partitions you may have. If you ACK...

Node process does not end and but CPU utilization at 100%

25

I have been investigating a problem that is causing trouble on our test suite and I managed to trace it to `mysql2`. This script allows reproducing it: Reproduction instructions ```js...

#374 - allow concurrent consumption of events

3

Closes https://github.com/ThreeDotsLabs/watermill/issues/374 ## Why? It would be nice to have a simple way to increase the concurrency of message processing. With the current options, it is only possible to consume...

Rebalances can lead to wrong lag being reported

2

**Describe the bug** When commits are not immediate and/or some events can have a relatively high processing time and topics substain a low traffic, it can lead to lag being...

#615 - allow specifying a listener for partition assignment changes

7

Closes https://github.com/segmentio/kafka-go/issues/615 Adds a listener to send re-assignments to a listener. After this, it is possible to possible to provide a listener (optional) to have consumers be notified of changes...

I have some code that returns: ``` { someProperty: 1, items: } ``` Randomly, I get things rendered like it follows: ``` { "someProperty": 1, "items": [ {"id": 1}, {"id":...

This is a skeleton PR aiming for discussion related to https://github.com/segmentio/kafka-go/issues/1308 In that issue, I describe how rebalances can lead to a situation where the consumer receiving the partition does...