{"push_id":1155799221,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"aa65de29ffc4492e4d5f62efc6a8f6da9aae40aa","before":"c0add99f3e60eae48264989197ddccb518b3ca6e","commits":[{"sha":"aa65de29ffc4492e4d5f62efc6a8f6da9aae40aa","author":{"name":"harsha","email":"e44e72979d6138121affd68488ade6d58f8e5f15@gmail.com"},"message":"MB-19783 Use barrier to prevent exit of long running task\n\nThere is a potential race in which terminator thread decides to\nterminate map reduce context and gets switched out of context.\nIn the meantime map reduce task is finished normally and the same\ncontext is reused to perform map reduce for subsequent mutations.\nNow terminator thread will potentially terminate this new task,\nwhen it is scheduled back to run.\nThis is avoided by using mutex in which either terminator thread,\nif successful will terminate long running map reduce task or the\ntask is terminated normally.\n\nChange-Id: I6785a4f12155eab637e924290889284050e13888\nReviewed-on: http://review.couchbase.org/64604\nTested-by: buildbot <build@couchbase.com>\nReviewed-by: Dave Finlay <dave.finlay@couchbase.com>\nReviewed-by: Dave Rigby <daver@couchbase.com>\nReviewed-by: Abhishek Singh <abhishek@couchbase.com>\nReviewed-by: Volker Mische <volker.mische@gmail.com>","distinct":true,"url":"https://api.github.com/repos/couchbase/couchdb/commits/aa65de29ffc4492e4d5f62efc6a8f6da9aae40aa"}]}
{"actor":{"display_login":"ns-codereview"}}