Hmm, I think Svante is correct, writes on disk-full would probably cause
the underlying file system to get in a bad state, and in that sense the
broker needs to be brought down for maintenance.
Guozhang
On Thu, Mar 26, 2015 at 3:49 PM, svante karlsson wrote:
> >4. As for recovering broker from
>4. As for recovering broker from disk full, if replication is enabled one
>can just bring it down (the leader of the partition will then migrate to
>other brokers), clear the disk space, and bring it up again; if replication
>is not enabled then you can first move the partitions away from this bro
Hi Bhavesh,
1. Server disk-full is treated the same as other error, that an error code
will be returned (in this case I think it is "Unknown" error though, as
disk IO exception is not specifically captured).
2. Upon receiving the error from the brokers, producer will retry based on
its configs. H
