Ok that's what we are already doing. In essence when that happens it is a bit like a rollover. Except depending on the values it might be the case that a consumer has a low enough value that web it requests the topic the value is still within range but is not valid since messages were delivered to the broker. Essentially it's a race condition that might be somewhat hard to induce but is theoretically possible. During a rollover of 64-bits this is more or less never going to happen because 64-bits is just too large to open a time window long enough for the race to occur.
On Nov 18, 2011, at 10:32 AM, Jun Rao <jun...@gmail.com> wrote: > Taylor, > > If you request an offset whose corresponding log file has been deleted, you > will get OutOfRange exception. When this happens, you can use the > getLatestOffset api in SimpleConsumer to obtain either the current valid > smallest or largest offset and reconsume from there. Our high level > consumer does that for you (among many other things). That's why we > encourage most users to use the high level api instead. > > Thanks, > > Jun
