{"push_id":615393078,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"da546b7ba03d84d7f6af97fe04471b12f5b3392f","before":"f43a61031fd7d9d4fab3d8ac584e7b4c7c5e1035","commits":[{"sha":"da546b7ba03d84d7f6af97fe04471b12f5b3392f","author":{"email":"5d14e010a5b345b784fd604efcc6cebb79f97468@gmail.com","name":"zsxwing"},"message":"[SPARK-6556][Core] Fix wrong parsing logic of executorTimeoutMs and checkTimeoutIntervalMs in HeartbeatReceiver\n\nThe current reading logic of `executorTimeoutMs` is:\n```Scala\nprivate val executorTimeoutMs = sc.conf.getLong(\"spark.network.timeout\",\n    sc.conf.getLong(\"spark.storage.blockManagerSlaveTimeoutMs\", 120)) * 1000\n```\nSo if `spark.storage.blockManagerSlaveTimeoutMs` is 10000 and `spark.network.timeout` is not set, executorTimeoutMs will be 10000 * 1000. But the correct value should have been 10000.\n\n`checkTimeoutIntervalMs` has the same issue.\n\nThis PR fixes them.\n\nAuthor: zsxwing <zsxwing@gmail.com>\n\nCloses #5209 from zsxwing/SPARK-6556 and squashes the following commits:\n\n6a0a411 [zsxwing] Fix docs\nc7d5422 [zsxwing] Add comments for executorTimeoutMs and checkTimeoutIntervalMs\nccd5147 [zsxwing] Fix wrong parsing logic of executorTimeoutMs and checkTimeoutIntervalMs in HeartbeatReceiver","distinct":true,"url":"https://api.github.com/repos/srowen/spark/commits/da546b7ba03d84d7f6af97fe04471b12f5b3392f"}]}