A read/write operation execution method, comprising: receiving (S901), by a first node, a first message and a second message from a second node, wherein the first message is for requesting to perform a read/write operation on a first address managed by a third node, the second message is for requesting to perform a read/write operation on a second address managed by the third node, wherein an execution sequence constraint of the read/write operation of the second node is stricter than an execution sequence constraint of the read/write operation of the third node; obtaining (S902), by the first node, operation permission of the first address and operation permission of the second address from the third node; and performing (S903), by the first node, read/write operations on the first address and the second address; characterised by when the first node requests the operation permission of the first address but does not obtain the operation permission of the first address, if the first node receives that the third node requests to perform a read/write operation that requires operation permission on the first address, or that the third node requests the operation permission of the first address, indicating, by the first node, to the third node that the operation permission of the first address is not obtained; and when the first node requests the operation permission of the second address but does not obtain the operation permission of the second address, if the first node receives that the third node requests to perform a read/write operation that requires operation permission on the second address, or that the third node requests the operation permission of the second address, indicating, by the first node, to the third node that the operation permission of the second address is not obtained. receiving (S901), by a first node, a first message and a second message from a second node, wherein the first message is for requesting to perform a read/write operation on a first address managed by a third node, the second message is for requesting to perform a read/write operation on a second address managed by the third node, wherein an execution sequence constraint of the read/write operation of the second node is stricter than an execution sequence constraint of the read/write operation of the third node; obtaining (S902), by the first node, operation permission of the first address and operation permission of the second address from the third node; and performing (S903), by the first node, read/write operations on the first address and the second address; characterised by when the first node requests the operation permission of the first address but does not obtain the operation permission of the first address, if the first node receives that the third node requests to perform a read/write operation that requires operation permission on the first address, or that the third node requests the operation permission of the first address, indicating, by the first node, to the third node that the operation permission of the first address is not obtained; and when the first node requests the operation permission of the second address but does not obtain the operation permission of the second address, if the first node receives that the third node requests to perform a read/write operation that requires operation permission on the second address, or that the third node requests the operation permission of the second address, indicating, by the first node, to the third node that the operation permission of the second address is not obtained. <EOS>