This is an educated guess... When a process dies "gracefully" there's a shutdown hook that closes the FileSystem. That can result in messages like this. It's likely there's an error before this about a zookeeper session being lost, or a halt issued by the master. See if this tserver died shortly after this message. If so, ignore the message.
-Eric On Fri, Nov 15, 2013 at 4:31 PM, Terry P. <[email protected]> wrote: > Greetings folks, > In my Accumulo 1.4.2 cluster I am seeing ERRORS about bloom loader threads > dying due to an rfile being closed. I can't copy/paste the error as it's > on an air-gapped system, but it starts with: > > ERROR Thread "bloom-loader-2147" died File > /accumulo/tables/2/t-0000aa4/F0000q3g.rf is closed > java.lang.IllegalStateException: File > /accumulo/tables/2/t-0000aa4/F0000q3g.rf is closed > at > org.apache.accumulo.core.file.blockfile.impl.CacheableBlockFile$Reader.getBCFile(CacheableBlockFile.java:244) > at > org.apache.accumulo.core.file.blockfile.impl.CacheableBlockFile$Reader.access$000(CacheableBlockFile.java:142) > (10 more java files ... ends with java.lang.Thread.run(UnknownSource) ) > > No real rhyme or reason as to when they occur; we are predominantly ingest > heavy with light reads by rowkey with ~10 entries per rowkey. I don't > really know if client programs are getting errors when these occur or not. > > I didn't find any JIRAs related to these. Should I be concerned about > these? >
