more logging for new EcoFS.ChunkIterator to find bug for

http://forum.yacy-websuche.de/viewtopic.php?f=6&t=1024&hilit=&p=6806#p6806

git-svn-id: https://svn.berlios.de/svnroot/repos/yacy/trunk@4652 6c8d7289-2bf4-0310-a012-ef5d649a1542
pull/1/head
orbiter 17 years ago
parent 4894df71ab
commit 5e4fddc1e6

@ -552,6 +552,7 @@ public class kelondroEcoFS {
try { try {
return stream != null && stream.available() > 0; return stream != null && stream.available() > 0;
} catch (IOException e) { } catch (IOException e) {
e.printStackTrace();
return false; return false;
} }
} }
@ -571,6 +572,7 @@ public class kelondroEcoFS {
} }
return chunk; return chunk;
} catch (IOException e) { } catch (IOException e) {
e.printStackTrace();
this.stream = null; this.stream = null;
return null; return null;
} }

@ -41,7 +41,7 @@ import de.anomic.kelondro.kelondroRow.Entry;
import de.anomic.server.serverMemory; import de.anomic.server.serverMemory;
/* /*
* The EcoIndex builts upon the EcoFS and tries to reduce the number of IO requests that the * The EcoIndex builds upon the EcoFS and tries to reduce the number of IO requests that the
* EcoFS must do to a minimum. In best cases, no IO has to be done for read operations (complete database shadow in RAM) * EcoFS must do to a minimum. In best cases, no IO has to be done for read operations (complete database shadow in RAM)
* and a rare number of write IO operations must be done for a large number of table-writings (using the write buffer of EcoFS) * and a rare number of write IO operations must be done for a large number of table-writings (using the write buffer of EcoFS)
* To make the EcoIndex scalable in question of available RAM, there are two elements that must be scalable: * To make the EcoIndex scalable in question of available RAM, there are two elements that must be scalable:

Loading…
Cancel
Save