[jira] [Updated] (HBASE-27125) The batch size of cleaning expired mob files should have an upper bound
[ https://issues.apache.org/jira/browse/HBASE-27125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huaxiang Sun updated HBASE-27125: - Fix Version/s: 2.4.13 (was: 2.4.14) > The batch size of cleaning expired mob files should have an upper bound > --- > > Key: HBASE-27125 > URL: https://issues.apache.org/jira/browse/HBASE-27125 > Project: HBase > Issue Type: Improvement > Components: mob >Affects Versions: 2.4.12 >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Minor > Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-3, 2.4.13 > > > Currently the cleaning logic for expired mob files is adding all the > deletable files in one directory to a list in memory and then archiving all > the files in the list. But when there are millions of files need to delete, > the list will be huge and make great heap memory pressure to the master. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27125) The batch size of cleaning expired mob files should have an upper bound
[ https://issues.apache.org/jira/browse/HBASE-27125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaolin Ha updated HBASE-27125: --- Release Note: Configure "hbase.master.mob.cleaner.batch.size.upper.bound" to set a proper batch size of cleaning expired mob files, its default value is 1. > The batch size of cleaning expired mob files should have an upper bound > --- > > Key: HBASE-27125 > URL: https://issues.apache.org/jira/browse/HBASE-27125 > Project: HBase > Issue Type: Improvement > Components: mob >Affects Versions: 2.4.12 >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Minor > Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-3, 2.4.14 > > > Currently the cleaning logic for expired mob files is adding all the > deletable files in one directory to a list in memory and then archiving all > the files in the list. But when there are millions of files need to delete, > the list will be huge and make great heap memory pressure to the master. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (HBASE-27125) The batch size of cleaning expired mob files should have an upper bound
[ https://issues.apache.org/jira/browse/HBASE-27125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kyle Purtell updated HBASE-27125: Fix Version/s: 2.4.14 (was: 2.4.13) > The batch size of cleaning expired mob files should have an upper bound > --- > > Key: HBASE-27125 > URL: https://issues.apache.org/jira/browse/HBASE-27125 > Project: HBase > Issue Type: Improvement > Components: mob >Affects Versions: 2.4.12 >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Minor > Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-3, 2.4.14 > > > Currently the cleaning logic for expired mob files is adding all the > deletable files in one directory to a list in memory and then archiving all > the files in the list. But when there are millions of files need to delete, > the list will be huge and make great heap memory pressure to the master. -- This message was sent by Atlassian Jira (v8.20.7#820007)
