{"push_id":669944730,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"5139f84bec5c4cef7f819da8415ff85ffe567777","before":"5fef06ebfaff4adeecb72ec0fa83e852640afc40","commits":[{"sha":"873f1abbb440aa60584c88ce876139005ed09a64","author":{"email":"b25b72a65195e46aa49449589ffbea257ff840a3@gmail.com","name":"Peter Mattis"},"message":"Fix handling of \"infinite\" clock offsets.\n\nInfinite clock offsets are generated when a heartbeat times (6s) out or\ntakes too long to finished (greater than 1.5s). Previously, such offsets\nwere treated as valid values as part of the cluster offset interval\ncalculation, but doing so meant that a sufficient number of slow nodes\nin a cluster (or a sufficiently slow network) would guarantee an\nunhealthy clock offset interval to be calculated.\n\nNow we never add \"infinite\" offsets to the clock offset monitor map. The\nmonitor is more pessimistic and will only suicide if the set of\ngood (non-infinite) clock offsets it has computes a cluster offset\ninterval that is larger than the max offset interval. If a node cannot\ntalk to any other nodes then its cluster offset interval will be\nconsidered healthy.","distinct":true,"url":"https://api.github.com/repos/cockroachdb/cockroach/commits/873f1abbb440aa60584c88ce876139005ed09a64"},{"sha":"e4eaad5637cb466e76ecc5d137516fa514de6c64","author":{"email":"b25b72a65195e46aa49449589ffbea257ff840a3@gmail.com","name":"Peter Mattis"},"message":"Completely remove proto.InfiniteOffset.","distinct":true,"url":"https://api.github.com/repos/cockroachdb/cockroach/commits/e4eaad5637cb466e76ecc5d137516fa514de6c64"},{"sha":"5139f84bec5c4cef7f819da8415ff85ffe567777","author":{"email":"4b8373d016f277527198385ba72fda0feb5da015@cockroachlabs.com","name":"Peter Mattis"},"message":"Merge pull request #1077 from cockroachdb/pmattis/infinite-clock-offset\n\nFix handling of \"infinite\" clock offsets.","distinct":true,"url":"https://api.github.com/repos/cockroachdb/cockroach/commits/5139f84bec5c4cef7f819da8415ff85ffe567777"}]}