On 13/06/12 13:25, Benson Margulies wrote:
Unfortunately, I've only seen this mishap once, over several (multi-hour) runs that get into trouble with memory.
If it is after a memory/GC problem, I'm afraid that all bets are off. This would be better with a better NodeTableTrans (the bit where I said I'd never seen an error in real life!) but at a fundamental level, the earlier problem is going to have knock-on effects.
Is the system preforming multiple concurrent updates?
Andy
