Staging instance, all changes can be removed at any time

Skip to content

Consumers are not notified of new assignements

Regression of the 1.5.1 / !271 (merged)

When a consumer rebalance happens, the current assignments are lost but the consumers are not notified of the new assignments. The results is the get_assignment falls in an never ending loop.

The result is there is only one consumer active at a time (the last one started)

objstorage-replayer-winery-5857bd4c94-wqsb8 objstorage-replayer INFO:swh.journal.client:No partition assigned, waiting for a new assignment
objstorage-replayer-winery-5857bd4c94-dpgjx objstorage-replayer INFO:swh.journal.client:No partition assigned, waiting for a new assignment
objstorage-replayer-winery-5857bd4c94-kgxbt objstorage-replayer INFO:swh.journal.client:No partition assigned, waiting for a new assignment
objstorage-replayer-winery-5857bd4c94-74rkz objstorage-replayer INFO:swh.journal.client:No partition assigned, waiting for a new assignment
objstorage-replayer-winery-5857bd4c94-qm574 objstorage-replayer INFO:swh.journal.client:No partition assigned, waiting for a new assignment