Deepthi Devaki Akkoorath

> I think the original issue is fixed, right? Yes. :+1:

As we are nearing code freeze for 8.1.0 release, we have left some issues for the next quarter. Following are some issues/improvements that we would not be able to get...

Closing this. A new issue will be created to keep track of the pending tasks and improvements.

This is failing quite frequently now.

Those are valid points. But let's keep it simple now. New brokers joining is currently not a supported feature. We could also treat data loss as a special case and...

Case 1 must be handled. We can decide what is the semantics of failure. The simplest would be to leave the cluster in a partial state - some brokers have...

> For the user (either human or some backup service) it's probably difficult to tell whether data loss has happened. The data loss shouldn't be treated like other failures like...

That said, if you have some idea how we can handle data loss scenario, we could discuss it. But as I said, I'm not sure if it is worth the...

> First thing that came to mind was to move the pause flag to ExportersState. This would be lost after the data loss as well, no?

> I've found one more issue that doesn't involve data loss: Not all brokers are members for all partitions. After a restart, the set of partitions that a broker is...