{"push_id":2604561466,"size":37,"distinct_size":2,"ref":"refs/heads/inc/events-redirect","head":"e3a4d09bea0c00be166675edc68041eb38b9b115","before":"d2e835b9896f4161d8017d2697a2a27d267e7f62","commits":[{"sha":"474012e8d5264edc6626a673fe31262423389e42","author":{"name":"Alena Varkockova","email":"ff019c5ab886bcb2d7b233532f59173c3efc3189@gmail.com"},"message":"Remove record method from MinMaxCounter (#6204)","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/474012e8d5264edc6626a673fe31262423389e42"},{"sha":"04f0137e1df0b4f55cbcf5333fb02e8b844ae1d5","author":{"name":"Alena Varkockova","email":"ff019c5ab886bcb2d7b233532f59173c3efc3189@gmail.com"},"message":"Measure group update queue size (#6199)\n\nJIRA issues: MARATHON-8197","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/04f0137e1df0b4f55cbcf5333fb02e8b844ae1d5"},{"sha":"5afbde86ac252b425e2a802ee44ce3589604d121","author":{"name":"Tim Harper","email":"fbcf19e3e699569a4900fe341b72674421e73f8b@mesosphere.io"},"message":"Async deployment responses (#6187)\n\nIn this change we convert deployment creating API methods to use Jersey 2 AsyncResponse. By doing this, we no longer timeout (\"Futures timed out\"); if a deployment takes 2 minutes to schedule, and the HTTP client does not have a shorter receive timeout configured, then the response will be delivered after 2 minutes. This is decidedly better than timing out server-side, responding as such, and then doing the work anyways.\r\n\r\nAlso, we consolidate some response logic, converging places where there where multiple response generators to just simply prefer the MarathonExceptionMapper instead.\r\n\r\nFurther, we introduce Rejection, which models unknown reasons why an API request will not be satisfied, and carries with it a guarantee that the exception mapper will know how to render a response for it.\r\n\r\nJIRA Issues: MARATHON-8174","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/5afbde86ac252b425e2a802ee44ce3589604d121"},{"sha":"ea55d4f6526eb9460f337f94450cb0d115d7f325","author":{"name":"Tim Harper","email":"fbcf19e3e699569a4900fe341b72674421e73f8b@mesosphere.io"},"message":"Surface exceptions thrown in any part of the election graph (#6183)\n\nJIRA Issues: MARATHON-8187","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/ea55d4f6526eb9460f337f94450cb0d115d7f325"},{"sha":"e2ed1e7ca30614ef846711f120fe87a028d85958","author":{"name":"Alena Varkockova","email":"ff019c5ab886bcb2d7b233532f59173c3efc3189@gmail.com"},"message":"Move repository call to instance tracker (#6177)\n\nSummary:\r\nTo make the instance update flow more readable we decided to change the flow of calls and move the InstanceRepository.store call from InstanceOpProcessor to InstanceTrackerActor that's called from the process method anyway and is already making sure the state is updated in the InstanceTrackerActor itself.\r\n\r\nThis PR tries to be as much backward compatible as possible so I was trying to keep all the logs in the places they were before as well as\r\n\r\nJIRA issues: MARATHON-8177","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/e2ed1e7ca30614ef846711f120fe87a028d85958"},{"sha":"287abe3f1a2d3a43205133ddcc2c4223c4a3363e","author":{"name":"Aleksey Dukhovniy","email":"6eabfc875f21416842705bf70a643836a5a28587@mesosphere.io"},"message":"Update apache curator dependency (#6195)\n\n- updated apache curator to 4.0.1\r\n- updated curator-test to 2.12.0","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/287abe3f1a2d3a43205133ddcc2c4223c4a3363e"},{"sha":"62b432eced2fe826950c528e1f91477b167ea2cd","author":{"name":"Nikita Melkozerov","email":"c99bb5f6142e0eb80cf93661810940ec4f7286cc@mesosphere.io"},"message":"Fix the behaviour of the GcActor in marathon (#6198)\n\nFix the behaviour of the GcActor in marathon\r\n\r\nSummary: implemented backpressured batched GC scans, so we don't consume too much memory at once. It stabilize marathon behaviour with lots of deployments.\r\n\r\nJIRA issues: MARATHON-8195","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/62b432eced2fe826950c528e1f91477b167ea2cd"},{"sha":"b8c7ff933ab05b94e6e4df60d030ad47a9eb410d","author":{"name":"Karsten Jeschkies","email":"13fbd79c3d390e5d6585a21e11ff5ec1970cff0c@jeschkies.xyz"},"message":"Report successful and failed loop builds. (#6209)\n\nSummary:\r\nWe missed a commit that caused flaky tests because the Marathon loop\r\nitself was not working. This change introduces a count metric in\r\nDataDog. We will set up a monitor that alarms if the number of\r\nsuccessful builds is below a certain threashold in the last 24hrs. In\r\nthe future we might want to add commit events so that we can triage the\r\nproblematic commits faster.\r\n\r\nJIRA issues: MARATHON-8199","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/b8c7ff933ab05b94e6e4df60d030ad47a9eb410d"},{"sha":"23ac0dc762a2abdaa8869f1ccfd4b957190f1b40","author":{"name":"Aleksey Dukhovniy","email":"6eabfc875f21416842705bf70a643836a5a28587@mesosphere.io"},"message":"Fix master loop failure metric (#6217)\n\nSummary:\r\n- fixed `marathon_loop_master.failure` metric which was previously sent in any case (instead of failure case)\r\n- added `marathon_loop_master.duration` to the metrics","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/23ac0dc762a2abdaa8869f1ccfd4b957190f1b40"},{"sha":"b99f58322003ecb5881ec00ee3c5cf9bb2cdb24d","author":{"name":"Tim Harper","email":"fbcf19e3e699569a4900fe341b72674421e73f8b@mesosphere.io"},"message":"Switch to Scalatest JUnitXMLReporter to regain the timestamp field (#6214)\n\nSummary:\r\nSBT 1.x ships with a JUnit XML reporter which is enabled, by\r\ndefault. Unfortunately, this reporter is missing a field which is\r\nexpected by Jenkins: timestamp. We use this field in our test analysis\r\ntool to reason about which tests ran in parallel.\r\n\r\nSwitching to the Scalatest JUnitXML reporter brings the field back for\r\nthe time being.\r\n\r\nSee https://github.com/sbt/sbt/issues/4153","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/b99f58322003ecb5881ec00ee3c5cf9bb2cdb24d"},{"sha":"c8cb747cccfe20a65ee7b2127a7b161b9b08ae38","author":{"name":"Ioannis Charalampidis","email":"cfc465e504939124d699f09edc42bd75d63680be@users.noreply.github.com"},"message":"Introduce HTTP input and output byte counters (#6197)\n\n* Introduce HTTP input and output byte counters\r\n\r\nThis commit introduces a new filter that replaces the input and output streams\r\nwith a proxy stream that counts the bytes exchanged.\r\n\r\nRelated JIRA: MARATHON-8158\r\n\r\n* Implementing the optimised stream methods\r\n\r\n* Renaming input/output wrappers to something more sensible\r\n\r\n* Making `bytes` property more descriptive\r\n\r\n* Adding integration test for the HTTP metrics\r\n\r\n* Renaming inputBytes/outputBytes to bytesRead/bytesWritten\r\n\r\n* Renaming the metrics counter on the integration tests\r\n\r\n* Fix HTTP traffic metrics calculation and integration tests.\r\n\r\nAdditionally, use JVM arguments when starting Marathon instances in IT.","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/c8cb747cccfe20a65ee7b2127a7b161b9b08ae38"},{"sha":"11f29e55a9fae293d904145ad47aba3a3a1a7ba0","author":{"name":"Aleksey Dukhovniy","email":"6eabfc875f21416842705bf70a643836a5a28587@mesosphere.io"},"message":"Add DataDog events for our SI test builds for every cluster variant (#6231)","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/11f29e55a9fae293d904145ad47aba3a3a1a7ba0"},{"sha":"dcda017df0e76dac8ac0358140ac1adf085614a6","author":{"name":"Ioannis Charalampidis","email":"cfc465e504939124d699f09edc42bd75d63680be@users.noreply.github.com"},"message":"Adding launchOperations, launchGroupOperations, reserveOperations (#6224)\n\nThis commit introduces the counters on the OfferOperationFactory that counts the\r\nlaunch, launch_group and reserve mesos operations of marathon.\r\n\r\nJIRA Issues: MARATHON-8213","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/dcda017df0e76dac8ac0358140ac1adf085614a6"},{"sha":"31812064efd87d07c9ba5d3bff28925f4eb9cc43","author":{"name":"Aleksey Dukhovniy","email":"6eabfc875f21416842705bf70a643836a5a28587@mesosphere.io"},"message":"Fix `si_pipeline` script (#6232)\n\nSummary:\r\n- fixed path for calling DataDog client\r\n- fixed gathering of DC/OS bundle\r\n- added ammonite dependency to `si_install_deps.sh` script","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/31812064efd87d07c9ba5d3bff28925f4eb9cc43"},{"sha":"90098f81ebcd7ece7a85cbb43b4e8c1369bad586","author":{"name":"Alena Varkockova","email":"ff019c5ab886bcb2d7b233532f59173c3efc3189@gmail.com"},"message":"Improve the message in case of failure (#6215)","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/90098f81ebcd7ece7a85cbb43b4e8c1369bad586"},{"sha":"1420101bffde8ac57bb8e19abf973defe8e0a070","author":{"name":"Ivan Chernetsky","email":"5bf8f0b3a82e63a56d5d2e680854267af1fe5d7a@mesosphere.io"},"message":"Add Marathon/Mesos compatibility matrix to the docs (#6207)\n\nJIRA issues: MARATHON-7680","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/1420101bffde8ac57bb8e19abf973defe8e0a070"},{"sha":"a3c4d993c82ebae5e307d28ee25cd22fe9ede04a","author":{"name":"Aleksey Dukhovniy","email":"6eabfc875f21416842705bf70a643836a5a28587@mesosphere.io"},"message":"Use Apache Curator `RetryPolicy` (#6218)\n\nSummary:\r\nwe were using our custom `Retry` logic in the `ZKPersistenceStore` class. This change replaces it with Curator `BoundedExponentialBackoffRetry` policy.\r\n\r\nAdditionally:\r\n- simplified `RichCuratorFramework.blockUntilConnected` method - an exception is immediately thrown if the connection to ZK fails\r\n- introduced 2 new parameters to control the retry policy: `zk_operation_max_retries` and `zk_operation_base_retry_sleep_ms`\r\n- removed some dead code","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/a3c4d993c82ebae5e307d28ee25cd22fe9ede04a"},{"sha":"81e227042bc0b178f3fb57bf42563fc73794e724","author":{"name":"Ioannis Charalampidis","email":"cfc465e504939124d699f09edc42bd75d63680be@users.noreply.github.com"},"message":"Fix AtomicGauge (#6227)\n\nThis commit fixes the `AtomicGauge` instance that is used explicitly by the\r\nInstaceTrackerActor to track the `running` and `staged` number of instances.\r\n\r\nA follow-up commit will introduce the `healthy` and` unhealthy` stats\r\n\r\nRelated JIRAs: MARATHON-8212","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/81e227042bc0b178f3fb57bf42563fc73794e724"},{"sha":"bbf66a902561452af214e632a79f0db10975762e","author":{"name":"Aleksey Dukhovniy","email":"6eabfc875f21416842705bf70a643836a5a28587@mesosphere.io"},"message":"Fix Mesos HTTP health check for non-host networking mode with `containerPort=0` (#6235)\n\nFixed a bug where for a container in non-host networking mode (`container` and `container/bridged`) with `hostPort=0, containerPort=0` we would set the `containerPort == hostPort` in `ContainerInfo` *and* ports environment variables *but not* in the `NetworkInfo`.\r\nAs the result Mesos health checks in this scenario would try to probe `containerPort == 0`. This behavior has now been unified for `NetworkInfo`, `ContainerInfo` and generated ports environment variables resulting in fixed Mesos HTTP health checks.","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/bbf66a902561452af214e632a79f0db10975762e"},{"sha":"64f6d068c8cdb460fb7e0ce0e750954e180cb2c9","author":{"name":"Aleksey Dukhovniy","email":"6eabfc875f21416842705bf70a643836a5a28587@mesosphere.io"},"message":"Run SI test builds every 2h (#6237)\n\nSummary:\r\nUpdated the SI pipeline triggers to run roughly every 2h. However we use Jenkins `H` cron job option (https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/triggers/TimerTrigger/help-spec.jelly#L40) for Jenkins to try to spread the load evenly. Overall we should end up with running approx. two SI jobs at any time which shouldn't be a problem.","distinct":false,"url":"https://api.github.com/repos/mesosphere/marathon/commits/64f6d068c8cdb460fb7e0ce0e750954e180cb2c9"}]}
{"actor":{"display_login":"ichernetsky"}}