{"push_id":3103176196,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"94b066bb3623ee386f24e1ac567303cdd5ee91a6","before":"7fee0ec15384f8301866d45788c31a058116df04","commits":[{"sha":"e60e9bfe6e3a81f90639f74c4a10790e46938d03","author":{"name":"Will Berkeley","email":"c74686ab413a71926fc1bc9d16ebfa30e619336a@gmail.org"},"message":"[tools] Add tool to dump memtrackers\n\nThis adds a new tool, `kudu diagnose dump_mem_trackers`, that dumps the\nmem-trackers information. It contains information equivalent to the\ntracker table on /mem-trackers. There's a new RPC introduced to support\nthis tool. Output both as JSON and as a table is supported. The table\noutput type flattens the tracker hierarchy, but it can be\nreconstructed from the 'id' and 'parent_id' columns.\n\nSome Kudu community members have reported to me they have started using\nthe /mem-trackers page to investigate performance and memory issues with\nKudu clusters, and having a way to get the same information in a form\namenable to programmatic searching, sorting, and filtering is\nconvenient. This tool can also serve as a starting point for more\nautomated analysis of the tracker information.\n\nThe particular advantage of the memtracker dump over, say, the data\ngenerated by heap sampling is that the memtracker shows where memory is\nowned. The sampling just shows where it was allocated in a call stack.\nSo, for example, using the memtracker information it's possible to tell\nvery quickly exactly which tablets are using a lot of memory in\nDeltaMemStores. Heap samples would indicate memory allocated in\nupdate-related code paths, but it would not be possible to tell which\ntablet replicas actually held the memory that was allocated.\n\nHere's a small sample of output in csv table format:\n\ntablet-2e02d00d46834b359c6ba0f8d471cbf9,server,-1,2318,2583\ntxn_tracker,tablet-2e02d00d46834b359c6ba0f8d471cbf9,67108864,0,0\nMemRowSet-1,tablet-2e02d00d46834b359c6ba0f8d471cbf9,-1,265,265\nDeltaMemStores,tablet-2e02d00d46834b359c6ba0f8d471cbf9,-1,265,265\ntablet-2d40450f6556485eab92f64f90756b61,server,-1,2318,2583\ntxn_tracker,tablet-2d40450f6556485eab92f64f90756b61,67108864,0,0\nMemRowSet-1,tablet-2d40450f6556485eab92f64f90756b61,-1,265,265\nDeltaMemStores,tablet-2d40450f6556485eab92f64f90756b61,-1,265,265\n\nThe columns are id,parent-id,limit,current_consumption,peak_consumption\njust like the table on /mem-trackers.\n\nChange-Id: I3e54f809bb6434b8d8e8c95771fe089c9da122d0\nReviewed-on: http://gerrit.cloudera.org:8080/11975\nTested-by: Kudu Jenkins\nReviewed-by: Adar Dembo <adar@cloudera.com>","distinct":true,"url":"https://api.github.com/repos/apache/kudu/commits/e60e9bfe6e3a81f90639f74c4a10790e46938d03"},{"sha":"94b066bb3623ee386f24e1ac567303cdd5ee91a6","author":{"name":"Yingchun Lai","email":"220f6941bdfda6d0f2812f04aed5dc877cb3b0a5@qq.com"},"message":"[docs] Fix error gflags\n\nChange-Id: Id7d846fbacdd294b13139cfc17dba095aae7aa3e\nReviewed-on: http://gerrit.cloudera.org:8080/12023\nTested-by: Kudu Jenkins\nReviewed-by: Adar Dembo <adar@cloudera.com>","distinct":true,"url":"https://api.github.com/repos/apache/kudu/commits/94b066bb3623ee386f24e1ac567303cdd5ee91a6"}]}
{"actor":{"display_login":"asfgit"}}