Elasticsearch does generally not write very large segments sequentially, so your fio load is likely not very representative. I would recommend trying with a random read/write load instead as I would expect that to better match an Elasticsearch load pattern.
I recall having seen issues with GlusterFS and NFS in the past but am not sure whether these issues persists.