{"push_id":748381552,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"14b0aa325875fa01cfce78ddade616ed13e7dea1","before":"5f4c3fad22c2d45609374d9c541482d85950cafa","commits":[{"sha":"c8b57f1bdc8401dd318aaa842ed3a2101f741182","author":{"email":"c8bdb43571a00f5e3218593bf1e2d71b2626cd7c@hazelcast.com","name":"Mehmet Dogan"},"message":"- Introduced max-lease-time (default is Long.MAX_VALUE ms) for locks. When lock is acquired without a explicit lease-time then max-lease-time setting will be used. Caller can use a lower value but not a greater one. When a greater lease-time is given, invocation/operation will fail immediately.\n\n- Fixed a bug which lease-time is not set correctly on backups and when backup is promoted, lease handling process doesn't kicks in.","distinct":true,"url":"https://api.github.com/repos/hazelcast/hazelcast/commits/c8b57f1bdc8401dd318aaa842ed3a2101f741182"},{"sha":"40a02f9d10fa7662ccbdb26a8187a9e67fda34ee","author":{"email":"c8bdb43571a00f5e3218593bf1e2d71b2626cd7c@hazelcast.com","name":"Mehmet Dogan"},"message":"Added tests for max-lock-lease-time property and lock-lease-time backup handling.","distinct":true,"url":"https://api.github.com/repos/hazelcast/hazelcast/commits/40a02f9d10fa7662ccbdb26a8187a9e67fda34ee"},{"sha":"14b0aa325875fa01cfce78ddade616ed13e7dea1","author":{"email":"b42a6d93d796915222f6ffb2ffdd6137d93c1cdb@hazelcast.com","name":"Ali"},"message":"Merge pull request #5603 from mdogan/lock-max-lease\n\nIntroduced lock max lease time","distinct":true,"url":"https://api.github.com/repos/hazelcast/hazelcast/commits/14b0aa325875fa01cfce78ddade616ed13e7dea1"}]}