{"push_id":1099293310,"size":2,"distinct_size":2,"ref":"refs/heads/topic/multimaster","head":"2c2c8bb19b3ce08aae8b06dcd388f6501439213c","before":"9eb02a3eacdf75bb5b40ec1be39cdb510e635fce","commits":[{"sha":"e49fb94f01d92dfa2d18339adafcbf660c8a3819","author":{"email":"6af10407fddc76635edee378451756fee65ed487@quantcast.com","name":"Mike Ovsiannikov"},"message":"Chunk server: fix hello resume by always reporting non stable chunks, even in the case if the chunks are in flight list, by moving pending in flight list check after non stable check. Presently chunk in pending hello notify can become non stable prior to chunk available completion / reply arrival in the case when stale chunks is issued by the meta server, and it has to be added to the meta server transaction log. The meta server might issue chunk [re=]allocate thus making chunk non stable, then if chunk server disconnects before receiving chunk stale chunks followed by available response, the available chunks will be added to the in flight list. Unconditionally bump generation count in the meta server state machine in the case of error / disconnect, to protect against carrying out stale RPCs. Change trace messages to be more uniform. Add stable verify flag to change chunk version display method.","distinct":true,"url":"https://api.github.com/repos/quantcast/qfs/commits/e49fb94f01d92dfa2d18339adafcbf660c8a3819"},{"sha":"2c2c8bb19b3ce08aae8b06dcd388f6501439213c","author":{"email":"6af10407fddc76635edee378451756fee65ed487@quantcast.com","name":"Mike Ovsiannikov"},"message":"Meta server: add stable verify flag to change version's display method, add trace message to show modified chunk processing in chunk server hello handling.","distinct":true,"url":"https://api.github.com/repos/quantcast/qfs/commits/2c2c8bb19b3ce08aae8b06dcd388f6501439213c"}]}