stoty commented on PR #6327: URL: https://github.com/apache/hbase/pull/6327#issuecomment-2411781562
As for the data collection, one alternative could be using a special CF for the statistics, instead of a separate table. That way the statistics could be stored right with the table, and with the correct rowkey design (i.e. prepending the region's start key) it would also be local to the same region server. Phoenix's local indexes use this trick. If write performance is a problem, the rowkey for the statistics table could also be salted. IUC we now have one cell per region per CF, so the the statistics write load might not even be an issue, it's a tradeoff between write and read performance, as usual. -- 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: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
