Description of problem: When the customer were attempting to restore critical data they experienced errors reading a chunk on Gluster Storage
Good morning The option is set to on as expected, the customer agrees to turn it off but as they are still restoring information they are worried about the impact this change can done. They are seeing poor performance on the reads so they are concerned about how this option could impact. Is it safe to execute it now? or should we wait till the restore finish ? Thanks Alicia
(In reply to amansan from comment #7) > Good morning > > The option is set to on as expected, the customer agrees to turn it off but > as they are still restoring information they are worried about the impact > this change can done. > > They are seeing poor performance on the reads so they are concerned about > how this option could impact. Turning off this option would result in slowdown of lookups. If there are lots of small files, then reading them would also become slow as opening an fd to read the file would involve lookup. However, if the number of files is less (like small number of large files), performance impact on reading files would be less. > > Is it safe to execute it now? or should we wait till the restore finish ? If cu is ok to live with this problem till restore is done, we can turn off the option post restore. However, if the problem is severely affecting them, they can turn off the option and see whether they can live with the resultant performance. > > Thanks > > Alicia
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (glusterfs bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:1462