Hi, guys I have some questions about the implementation of rgw multisite. Hope anyone can give me some enlightenment. 1. RGWHTTPManager only has one thread to process libcurl read/write callbacks, will a multi-thread version be added in the future? 2. Data sync between rgw zones only use atomic put, will a multipart put version be considered in the future? 3. Cloud sync has a multipart put implementation, but no breakpoint resume, will this feature be added in the future? 4. Why not use spawn method instead of call method in RGWAWSStreamObjToCloudMultipartCR::operate() when do multipart put in the for loop for concurrency? For question 2, I have a preliminary idea: When zone1 want sync data in zone2, firstly, zone1 send a rest api request to zone2, maybe a new api or old api with extra rgwx header. Then, zone2 listen on that api and do the multipart put to zone1 in separate threads, maybe a manager thing like RGWDataChangesLog. Finally, zone1 can confirm it has finished sync for a specified object after receiving a multipart-complete request with an extra header from zone2. How about this idea? Is that right? Thanks. -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
