Looks like a problem with caching. Can you please try by disabling all performance translators? The following configuration commands would disable performance translators in the gluster client stack:
gluster volume set <volname> performance.quick-read off gluster volume set <volname> performance.io-cache off gluster volume set <volname> performance.write-behind off gluster volume set <volname> performance.stat-prefetch off gluster volume set <volname> performance.read-ahead off gluster volume set <volname> performance.readdir-ahead off gluster volume set <volname> performance.open-behind off gluster volume set <volname> performance.client-io-threads off Thanks, Vijay On Mon, May 22, 2017 at 9:46 AM, Christopher Schmidt <fakod...@gmail.com> wrote: > Hi all, > > has anyone ever successfully deployed a Kafka (Cluster) on GlusterFS > volumes? > > I my case it's a Kafka Kubernetes-StatefulSet and a Heketi GlusterFS. > Needless to say that I am getting a lot of filesystem related exceptions > like this one: > > Failed to read `log header` from file channel > `sun.nio.ch.FileChannelImpl@67afa54a`. > Expected to read 12 bytes, but reached end of file after reading 0 bytes. > Started read from position 123065680. > > I limited the amount of exceptions with the log.flush.interval.messages=1 > option, but not all... > > best Christopher > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
