Techniques for identifying IO hot spots using range-lock information

• US 8,954,699 B1
• Filed: 06/28/2012
• Issued: 02/10/2015
• Est. Priority Date: 06/28/2012
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Chen, Xiangping, Armangau, Philippe
• Primary Examiner(s): CHOE, YONG J
• Application Number:
  US13/536,389
• Time in Patent Office: 957 Days
• Field of Search: 711/165, 711/161, 711/162, 711/163, 711/167
• US Class Current: 711/165
• CPC Class Codes: G06F 11/3034 where the computing system component is a storage system, e.g. DASD based or network based digital input from or digital output to record carriers G06F3/06; digital recording or reproducing G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097
• CPC Class Codes: G06F 11/3471 Address tracing
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 2201/825 the problem or solution involving locking

Abstract

A technique of identifying IO hot spots is performed in a data storage apparatus (e.g., a file server). The technique involves updating, in response to host IO operations which lock ranges of extents prior to accessing the ranges of extents, contents of a lock history database based on the ranges of extents which were locked by the host IO operations. The technique further involves receiving a lock history request. The technique further involves providing, in response to the lock history request, the contents of the lock history database to identify, as the IO hot spots, extents which were locked by the host IO operations.

Claims

1. In a data storage apparatus, a method of identifying input/output (IO) hot spots, the method comprising:

in response to host IO operations which lock ranges of extents prior to accessing the ranges of extents, updating contents of a lock history database based on the ranges of extents which were locked by the host IO operations;

receiving a lock history request; and

in response to the lock history request, providing the contents of the lock history database to identify, as the IO hot spots, extents which were locked by the host IO operations;

wherein the lock history database includes range-lock entries, each range-lock entry identifying a respective host IO operation and a respective range of extents which was locked by the respective host IO operation; and

wherein updating the contents of the lock history database includes;

receiving an IO event message indicating a particular host IO operation and a particular range of extents which was locked by the particular host IO operation, and

adding a new range-lock entry to the lock history database, the new range-lock entry identifying the particular host IO operation and the particular range of extents which was locked by the particular host IO operation.

2. A method as in claim 1 wherein each range-lock entry includes a lock type field, a storage object identifier field, a time stamp field, and a set of range fields;

and wherein adding the new range-lock entry to the lock history database includes;

placing a lock type value in the lock type field of the new range-lock entry, the lock type value indicating whether the particular host IO operation imposed a read lock or a write lock on the particular range of extents,

placing a storage object identifier in the storage object identifier field of the new range-lock entry, the storage object identifier identifying a particular storage object among multiple storage objects maintained for reading and writing by the data storage apparatus,

placing a time stamp in the time stamp field of the new range-lock entry, the time stamp indicating a particular time in which the particular host IO operation locked the particular range of extents, and

placing range data in the set of range fields to identify the particular range of extents which was locked by the particular host IO operation.

3. A method as in claim 2, further comprising:

storing the contents of the lock history database in non-volatile memory of the data storage apparatus to persist the contents of the lock history database during a reboot of the data storage apparatus.

4. A method as in claim 3, further comprising:

receiving a reset request and clearing the contents of the lock history database stored in the non-volatile memory in response to the reset request.

5. A method as in claim 1 wherein providing the contents of the lock history database includes:

outputting, as the contents of the lock history database, the range-lock entries to enable analysis of range-lock statistics defined by the respective host IO operations and the respective ranges of extents identified by the range-lock entries.

6. A method as in claim 1 wherein the lock history database further includes aggregated lock data;

and wherein the method further comprises;

adjusting the aggregated lock data of the lock history database based on the range-lock entries of the lock history database and, after the aggregated lock data is adjusted, removing the range-lock entries from the lock history database to consolidate the lock history database.

7. A method as in claim 6 wherein providing the contents of the lock history database includes:

outputting, as the contents of the lock history database, the aggregated lock data to enable analysis of range-lock statistics defined by the respective host IO operations and the respective ranges of extents identified by the range-lock entries.

8. A method as in claim 6, further comprising:

periodically adjusting the aggregated lock data based on new range-lock entries of the lock history database to consolidate the lock history database in an ongoing manner.

9. A method as in claim 1 wherein the data storage apparatus includes processing circuitry which is constructed and arranged to operate as (i) a range lock module which imposes read locks and write locks on ranges of extents, and (ii) a lock history module which manages the lock history database;

wherein the method further comprises providing, by the processing circuitry while the processing circuitry operates as the range lock module, a procedure call from the range lock module to the lock history module, the procedure call providing the IO event message; and

wherein receiving the IO event message and adding the new range-lock entry to the lock history database are performed by the processing circuitry while the processing circuitry operates as the lock history module.

10. A method as in claim 1 wherein the data storage apparatus includes processing circuitry which is constructed and arranged to operate as (i) a lock history module which manages the lock history database, and (ii) a service module which accesses the lock history module via procedure calls;

wherein receiving the IO event message and adding the new range-lock entry to the lock history database are performed by the processing circuitry while the processing circuitry operates as the lock history module; and

wherein the method further comprises providing, by the processing circuitry while the processing circuitry operates as the service module, a procedure call from the service module to the lock history module, the procedure call providing the lock history request to obtain the contents of the lock history database.

11. A method as in claim 1 wherein the data storage apparatus includes processing circuitry which is constructed and arranged to operate as (i) a range lock module which imposes read locks and write locks on ranges of extents, (ii) a lock history module which manages the lock history database, and (iii) a service module which accesses the lock history module via procedure calls;

wherein the method further comprises providing, by the processing circuitry while the processing circuitry operates as the range lock module, a first procedure call from the range lock module to the lock history module, the first procedure call providing the IO event message;

wherein receiving the IO event message and adding the new range-lock entry to the lock history database are performed by the processing circuitry while the processing circuitry operates as the lock history module; and

wherein the method further comprises providing, by the processing circuitry while the processing circuitry operates as the service module, a second procedure call from the service module to the lock history module, the second procedure call providing the lock history request to obtain the contents of the lock history database.

12. A method as in claim 1 wherein the data storage apparatus includes (i) host storage within which the extents reside and (ii) other storage within which the lock history database resides, the other storage being different from the host storage;

and

wherein providing the contents of the lock history database in response to the lock history request includes outputting metadata from the other storage which is different from the host storage within which the extents reside.

13. A method as in claim 12 wherein the host storage includes a fast storage tier and a slow storage tier;

and wherein the method further comprises;

moving host data from the slow storage tier to the fast storage tier based on the provided contents of the lock history database.

14. A method as in claim 12 wherein the host storage includes a fast storage tier and a slow storage tier;

and wherein the method further comprises;

moving host data from the fast storage tier to the slow storage tier based on the provided contents of the lock history database.

15. A data storage apparatus, comprising:

a host interface;

memory which stores a lock history database; and

processing circuitry coupled to the host interface and the memory, the processing circuitry being constructed and arranged to;

update, in response to host input/output (IO) operations which lock ranges of extents prior to accessing the ranges of extents, contents of the lock history database based on the ranges of extents which were locked by the host IO operations,

receive a lock history request, and

in response to the lock history request, provide the contents of the lock history database to identify, as IO hot spots, extents which were locked by the host IO operations;

wherein the lock history database includes range-lock entries, each range-lock entry identifying a respective host IO operation and a respective range of extents which was locked by the respective host IO operation; and

wherein the processing circuitry, when updating the contents of the lock history database, is constructed and arranged to;

receive an IO event message indicating a particular host IO operation and a particular range of extents which was locked by the particular host IO operation, and

add a new range-lock entry to the lock history database, the new range-lock entry identifying the particular host IO operation and the particular range of extents which was locked by the particular host IO operation.

16. A data storage apparatus as in claim 15 wherein each range-lock entry includes a lock type field, a storage object identifier field, a time stamp field, and a set of range fields;

and wherein the processing circuitry, when adding the new range-lock entry to the lock history database, is constructed and arranged to;

place a lock type value in the lock type field of the new range-lock entry, the lock type value indicating whether the particular host IO operation imposed a read lock or a write lock on the particular range of extents,

place a storage object identifier in the storage object identifier field of the new range-lock entry, the storage object identifier identifying a particular storage object among multiple storage objects maintained for reading and writing by the data storage apparatus,

place a time stamp in the time stamp field of the new range-lock entry, the time stamp indicating a particular time in which the particular host IO operation locked the particular range of extents, and

place range data in the set of range fields to identify the particular range of extents which was locked by the particular host IO operation.

17. A data storage apparatus as in claim 15 wherein the memory includes (i) host storage within which the extents reside and (ii) other storage within which the lock history database resides, the other storage being different from the host storage;

and

wherein the processing circuitry, when providing the contents of the lock history database in response to the lock history request, is constructed and arranged to output metadata from the other storage which is different from the host storage within which the extents reside.

18. A computer program product which has a non-transitory computer readable medium storing a set of instructions which, when executed by a computerized device, cause the computerized device to perform a method comprising:

updating, in response to host input/output (IO) operations which lock ranges of extents prior to accessing the ranges of extents, contents of a lock history database based on the ranges of extents which were locked by the host IO operations;

receiving a lock history request; and

in response to the lock history request, providing the contents of the lock history database to identify, as the IO hot spots, extents which were locked by the host IO operations;

wherein the lock history database includes range-lock entries, each range-lock entry identifying a respective host IO operation and a respective range of extents which was locked by the respective host IO operation; and

wherein updating the contents of the lock history database includes;

receiving an IO event message indicating a particular host IO operation and a particular range of extents which was locked by the particular host IO operation, and

adding a new range-lock entry to the lock history database, the new range-lock entry identifying the particular host IO operation and the particular range of extents which was locked by the particular host IO operation.

19. A computer program product as in claim 18 wherein each range-lock entry includes a lock type field, a storage object identifier field, a time stamp field, and a set of range fields;

and wherein adding the new range-lock entry to the lock history database includes;

placing a lock type value in the lock type field of the new range-lock entry, the lock type value indicating whether the particular host IO operation imposed a read lock or a write lock on the particular range of extents,

placing a storage object identifier in the storage object identifier field of the new range-lock entry, the storage object identifier identifying a particular storage object among multiple storage objects maintained for reading and writing by the data storage apparatus,

placing a time stamp in the time stamp field of the new range-lock entry, the time stamp indicating a particular time in which the particular host IO operation locked the particular range of extents, and placing range data in the set of range fields to identify the particular range of extents which was locked by the particular host IO operation.

20. A computer program product as in claim 18 wherein the computerized device includes (i) host storage within which the extents reside and (ii) other storage within which the lock history database resides, the other storage being different from the host storage;

and

wherein providing the contents of the lock history database in response to the lock history request includes outputting metadata from the other storage which is different from the host storage within which the extents reside.