{"push_id":1030321262,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"62fb544224178377990752b16956ee2e13d9207c","before":"919608caaf1852661aa2809b75817a845c0130ee","commits":[{"sha":"d456d9e934d8eb845d83b1e0c29247aac87e2e92","author":{"email":"3e53127f3ad0d91a1ed4651b133d989b076d9d27@hp.com","name":"Alistair Coles"},"message":"Don't ssync data when only a durable is missing\n\nIf an EC diskfile is missing its .durable file (for example\ndue to a partial PUT failure) then the ssync missing check\nwill fail to open the file and will consider it\nmissing. This can result in possible reconstruction of the\nfragment archive (for a sync job) and definite transmission\nof the fragment archive (for sync and revert jobs), which is\nwasteful.\n\nThis patch makes the ssync receiver inspect the diskfile\nstate after attempting to open it, and if fragments exist at\nthe timestamp of the sender's diskfile, but a .durable file\nis missing, then the receiver will commit the diskfile at\nthe sender's timestamp. As a result, there is no longer any\nneed to send a fragment archive.\n\nChange-Id: I4766864fcc0a3553976e8fd85bbb2fc782f04abd","distinct":true,"url":"https://api.github.com/repos/openstack/swift/commits/d456d9e934d8eb845d83b1e0c29247aac87e2e92"},{"sha":"62fb544224178377990752b16956ee2e13d9207c","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"Don't ssync data when only a durable is missing\"","distinct":true,"url":"https://api.github.com/repos/openstack/swift/commits/62fb544224178377990752b16956ee2e13d9207c"}]}