Hi, This is more of a thought question than a problem that I need support for. I have trying out Kafka 0.8.0-beta1 with replication. For our user case we want to try and guarantee that our consumers will see all messages even if they have fallen greatly behind the broker/producer. For this reason I wanted to know how the broker would react when the filesystem it writes its messages to is full. What I found was that the broker crashes and cannot be started until the filesystem has space again.
Is there or would it make sense to provide configuration allowing the broker to reject writes in this case rather than crashing, electing a new leader and attempting the write again? I can clearly understand the use case that we don't want to 'lose' messages from the producer and I could also see how lack of filesystem space could be considered a machine failure, but with replication I would think if you are running out of space on 1 broker you are likely running out of space on others. Bryan
