Method, system and related components for managing inode cache space

Abstract

The present application discloses a method for managing an inode cache space. The management method includes: when detecting that the target file is closed, the client sets the state of the inode cache corresponding to the target file in the cache to an aging state, and records the The duration that the inode cache is in the aging state; determine whether the duration is greater than a preset value; if so, release the inode cache in the client, so that the server releases the cache space corresponding to the inode cache . This method can reasonably reclaim the inode cache space and save hardware cost. The application also discloses a management system of inode cache space, a computer-readable storage medium and an electronic device, which have the above beneficial effects.

Description

technical field [0001] The invention relates to the field of data storage management, in particular to a method and system for managing an inode cache space, a computer-readable storage medium and an electronic device. Background technique [0002] When the client interacts with the metadata service of the server, the client loads the inode (index node) that needs to be operated into its own cache. After the metadata service obtains the inode data, it also loads the related inode into the metadata cache. But now after the client finishes operating the inode (such as opening a file, closing it after modifying and saving), it will still hold the inode, and only modify the permission to operate the inode, but the inode will not be cleaned up on the client side cache. The advantage of this is that the inode can be directly stored in the cache during the next access, and the access speed will be faster. But this causes the inode to always be held in the metadata cache of the se...

AI Technical Summary

Problems solved by technology

But this causes the inode to always be held in the metadata cache of the server

When the metadata service of a server is connected to multiple clients, each client's own cache may not exceed the limit, but the cache inodes of the metadata service are more and more, which cannot be pruned at all, and there are metadata The service cache is too full

In the long run, the cache will become larger and larger, and the hardware cost will be high

Images