cshannon commented on issue #5014: URL: https://github.com/apache/accumulo/issues/5014#issuecomment-2495543314
> Would the following be a good way to handle upgrade? > > 1. Upgrade marks all splits as system > 2. There is per table prop that will enable automatic merges based on size. The default value for this property is disables automatic merging. > 3. The add split API call is modified such that if a user calls it passes in an existing split that is a system split it will remark it as a user split. > > Then after upgrade user have a chance to mark splits that should never be automatically removed before enabling the auto merge feature. I was wondering about the upgrade case, i like the idea of using absent for system splits as most splits will be system splits. However, one downside is any existing splits that a user created would be incorrectly marked as a system split on upgrade unless there were manual steps down like mentioned during upgrade. I think this is fine but I'm wondering how we make it easy for a user to mark splits. We might need a new command line tool or something to make it simple to mark them. In fact, I could use a use case where a user decides maybe there's some tablets they don't want merged (even if originally system created) and they could use the tool not just for upgrades but for marking those to prevent merging too. -- 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]
