----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36632/#review92761 -----------------------------------------------------------
A jira ticket needs to be filed on the geode project and then the jira number (GEODE-xxx) needs to be referred to in this review and in your git revision comment. Some of the info in the trac ticket 52441 should be included but just the info that would make sense to the geode community. - Darrel Schneider On July 22, 2015, 10:36 p.m., Namrata Thanvi wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/36632/ > ----------------------------------------------------------- > > (Updated July 22, 2015, 10:36 p.m.) > > > Review request for geode and Swapnil Bawaskar. > > > Repository: geode > > > Description > ------- > > calling setUsageThreshold() on MemoryPoolMXBean resulted in it reporting > incorrect memory usage causing temporary spikes. Since we already set > CollectionThreshold? at 1 byte and also have a stat and heap poller thread, > we now skip setting the usage threshold. [fixes bug 49064] > > tests run: precheckin, hdfs.bt > > > Diffs > ----- > > > gemfire-core/src/main/java/com/gemstone/gemfire/internal/cache/control/HeapMemoryMonitor.java > 83462456ccce093dc75661e00ac45888417d434a > > Diff: https://reviews.apache.org/r/36632/diff/ > > > Testing > ------- > > yes. > > > Thanks, > > Namrata Thanvi > >
