{"push_id":2909170175,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ce145ffee6ee68a60c4ef663cb9f47f22d9eb19f","before":"df53ec2385190bba2b3cefb43b094cde6d33642f","commits":[{"sha":"ce145ffee6ee68a60c4ef663cb9f47f22d9eb19f","author":{"name":"Tim Armstrong","email":"2f8e34250f03a653da3dc27f7ec203eafdde80fc@cloudera.com"},"message":"IMPALA-7600: bump mem_limit for test_kudu_scan_mem_usage\n\nThe estimate for memory consumption for this scan is 9 columns * 384kb\nper column = 3.375mb. So if we set the mem_limit to 6.5mb, we should\nstill not get more than one scanner thread, but we can avoid hitting\nout-of-memory.\n\nThe issue in the JIRA was queued row batches. With this change, and\nnum_scanner_threads=2, there should be max 12 row batches\n(10 in the queue, 2 in the scanner threads about to be enqueued)\nand based on the column stats I'd estimate that each row batch is\naround 200kb, so this change should provide significantly more headroom.\n\nChange-Id: I6d992cc076bc8678089f765bdffe92e877e9d229\nReviewed-on: http://gerrit.cloudera.org:8080/11513\nReviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>\nTested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>","distinct":true,"url":"https://api.github.com/repos/apache/impala/commits/ce145ffee6ee68a60c4ef663cb9f47f22d9eb19f"}]}
{"actor":{"display_login":"asfgit"}}