On Thu, Jul 25, 2024 at 1:09 AM Joanne Koong <joannelkoong@xxxxxxxxx> wrote: > > On Wed, Jul 24, 2024 at 12:12 AM Yafang Shao <laoar.shao@xxxxxxxxx> wrote: > > > > In our experience with fuse.hdfs, we encountered a challenge where, if the > > HDFS server encounters an issue, the fuse.hdfs daemon—responsible for > > sending requests to the HDFS server—can get stuck indefinitely. > > Consequently, access to the fuse.hdfs directory becomes unresponsive. > > The current workaround involves manually aborting the fuse connection, > > which is unreliable in automatically addressing the abnormal connection > > issue. To alleviate this pain point, we have implemented a timeout > > mechanism that automatically handles such abnormal cases, thereby > > streamlining the process and enhancing reliability. > > > > The timeout value is configurable by the user, allowing them to tailor it > > according to their specific workload requirements. > > > > Signed-off-by: Yafang Shao <laoar.shao@xxxxxxxxx> > > Hi Yafang, > > There was a similar thread/conversation about timeouts started in this > link from last week > https://lore.kernel.org/linux-fsdevel/20240717213458.1613347-1-joannelkoong@xxxxxxxxx/#t > I am not currently subscribed to linux-fsdevel, so I missed your patch. Thanks for your information. I will test your patch. > The core idea is the same but also handles cleanup for requests that > time out, to avoid memory leaks in cases where the server never > replies to the request. For v2, I am going to add timeouts for > background requests as well. Please CC me if you send new versions. -- Regards Yafang
