keith-turner opened a new issue, #3648: URL: https://github.com/apache/accumulo/issues/3648
**Is your feature request related to a problem? Please describe.** Accumulo defines the GC batch size as a fixed memory amount [in its default config](https://github.com/apache/accumulo/blob/db1518538de0b922d2b93c156894e5dee2e3d9c1/core/src/main/java/org/apache/accumulo/core/conf/Property.java#L730). When there is a large amount of metadata relative this batch size it can result in inefficient GC cycles. When the process where GC is running has more memory this could be avoided. **Describe the solution you'd like** Accumulo configuration supports defining properties in terms of a percentage of memory [like this property](https://github.com/apache/accumulo/blob/db1518538de0b922d2b93c156894e5dee2e3d9c1/core/src/main/java/org/apache/accumulo/core/conf/Property.java#L376). Using a memory percentage instead of a fixed size would allow GC to be more efficient when more memory is available to it. The default value could be something like 50% that should leave plenty of space in the process. If this change is made it would also be nice to have the GC process log how much memory it is actually using for the candidates on startup. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
