keith-turner commented on issue #4074: URL: https://github.com/apache/accumulo/issues/4074#issuecomment-1856491382
With the changes in #4033 the default config could be single compaction service with two queues one for small and one for large compactions. All tables would be configured to use this single service by default. The default compaction service config may move from the java default properties class to documentation and the accumulo.properties that ships with the tarball. If this change is made the then java code would define no compaction services by default. However tables would still have default config for selecting a compaction service. So only having to define a single default compaction service in default config might be nice. I am not advocating for anything in this message, just thinking out loud. One thing I struggle with is trying to find a balance between simple config to get a small accumulo instance running vs whats good for large instances. I lean towards making the default config be suited to small clusters and making recommendations for config for large clusters easily discoverable. One way to achieve this is making the default compaction service config in accumulo.properties in the tar ball super simple and also provide a link in accumulo.properties in comments to documentation related to scaling accumulo that goes over how to dedicate resources for things like accumulo.root and accumulo.metadata. -- 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]
