Roll back GenerateBlobID. I will implement create objectID from virtual address in the future. Directly use virtual address and instance id as the blob ID will trigger error when vineyardd triggers spill. Because the GenerateBlobID function will assign a assigned ObjectID to a new object when put a cold object to disk.(Because there is no change of the object virtual address and the instance id )
Split big size data transfer with rdma into multiple small size data transfer.
Register memory when use RDMA to get/create remote object.(To solve the problem of mr's limit.)
What do these changes do?
Done:
Todo:
Related issue number
Fixes #1895