{"push_id":1417214096,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"3068870ccec689bc72039ac69ef1ebc9af4427f7","before":"734e4acafbcea77934d5164c424b5084f0422c82","commits":[{"sha":"3068870ccec689bc72039ac69ef1ebc9af4427f7","author":{"name":"Karthikeyan Radhakrishnan","email":"070753c865719f61a9d6b4f3dab85fced53be7e6@fb.com"},"message":"Making persistent cache more resilient to filesystem failures\n\nSummary:\nThe persistent cache is designed to hop over errors and return key not found. So far, it has shown resilience to write errors, encoding errors, data corruption etc. It is not resilient against disappearing files/directories. This was exposed during testing when multiple instances of persistence cache was started sharing the same directory simulating an unpredictable filesystem environment.\n\nThis patch\n\n- makes the write code path more resilient to errors while creating files\n- makes the read code path more resilient to handle situation where files are not found\n- added a test that does negative write/read testing by removing the directory while writes are in progress\nCloses https://github.com/facebook/rocksdb/pull/1472\n\nDifferential Revision: D4143413\n\nPulled By: kradhakrishnan\n\nfbshipit-source-id: fd25e9b","distinct":true,"url":"https://api.github.com/repos/facebook/rocksdb/commits/3068870ccec689bc72039ac69ef1ebc9af4427f7"}]}
{"actor":{"display_login":"facebook-github-bot"}}