we really need to know what the file history is. if it's a freshly flushed file, that's Bad.
if it's a file that was a compaction victim, that's annoying but not something we need to worry about. both flush and compaction are logged at INFO. On Sun, May 16, 2010 at 11:13 AM, Mason Hale <ma...@onespot.com> wrote: > Grepping through the logs, I haven't been able to deduce what was going on > at the same time, but I have found many instances of these errors for > multiple files going back for weeks nows. (Found 848 of these errors since > 4-23-2010). The files not found include Index and Data files spanning > multiple column families. > Where should I go from here? > > > On Sat, May 15, 2010 at 10:06 AM, Jonathan Ellis <jbel...@gmail.com> wrote: >> >> grep for Entry-28-Index.db in the logs, see what was going on before >> the exceptions. (was it compacted?) >> > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
