5efb08cd7b
The copyFile method has some safeguards to ensure that the multipart write is aborted. This is accomplished by always calling abort on the MultiWriteHandle when the copy is finished, whether or not there was a failure or it was successfully committed. If the copy was committed, then this RPC is a no-op on the metainfo server. Regardless, the calls to abort to constitute an additional RPC to the satellite for no benefit. This is exacerbated by the fact that the code currently ends up calling abort twice. This change updates the libuplink-backed MultiWriteHandle implementation to not call abort if the write is committed and vice-versa. This eliminates the two wasteful RPC calls. Change-Id: I13679234f6f473e9a93179e6791fb57eac512f25 |
||
|---|---|---|
| .. | ||
| buffer_test.go | ||
| buffer.go | ||
| filesystem.go | ||
| handle_file.go | ||
| handle_generic.go | ||
| handle_std_test.go | ||
| handle_std.go | ||
| handle_uplink.go | ||
| helpers_iterator.go | ||
| local_backend_mem.go | ||
| local_backend_os.go | ||
| local.go | ||
| mixed.go | ||
| remote.go | ||