EdColeman commented on issue #4529: URL: https://github.com/apache/accumulo/issues/4529#issuecomment-2096739546
elasticity added at table for FATEs. Maybe we would want a more general utility table instead of creating specific tables for each use? Later, if performance showed that there is contention on the utility table, it could be then split into separate tables? Using fewer tables may lead to easier management? For example, if designated servers are used for the metadata table, it may be desirable to collocate the utility table(s) to the same servers. This could come at the expense of more contention, but generally, the individual tables should be small relative to data tables, so there might not be a measurable impact if it was one table. If a utility table is used, it may help if the design allowed for easy spiting by using variables / properties for the table name instead of them being hard coded? -- 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]
