I’m assuming you are using the Flume Persistent Appender which uses Berkeley DB
based on the logs below. From the log it appears that Berkeley DB’s file
handle is stale and meets to be closed and reopened. I haven’t checked but
Berkeley DB might have a setting for this, otherwise the Flume Per
We use the Flume Appender. Our logging stopped after a certain point in
time and we noticed the exception at the end of this message in our
application logs. It looks like there was an issue with the filesystem. But
although the filesystem has recovered, the appender (or probably the
persistence me
