[ https://issues.apache.org/jira/browse/HBASE-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878827#comment-13878827 ]
Nick Dimiduk commented on HBASE-10392: -------------------------------------- Ah you're right. I missed the occurrence in MemStoreFlusher. Currently it respects both the old and new parameter. Maybe we could continue respecting new or old but print a warning if the old is used? I'll update the patch to do that and we'll see what folks think. > Correct references to hbase.regionserver.global.memstore.upperLimit > ------------------------------------------------------------------- > > Key: HBASE-10392 > URL: https://issues.apache.org/jira/browse/HBASE-10392 > Project: HBase > Issue Type: Bug > Reporter: Nick Dimiduk > Assignee: Nick Dimiduk > Fix For: 0.99.0 > > Attachments: HBASE-10392.0.patch > > > As part of the awesome new HBASE-5349, a couple references to > {{hbase.regionserver.global.memstore.upperLimit}} was missed. Clean those up > to use the new {{hbase.regionserver.global.memstore.size}} instead. -- This message was sent by Atlassian JIRA (v6.1.5#6160)