Jibing-Li commented on code in PR #37715:
URL: https://github.com/apache/doris/pull/37715#discussion_r1676047767
##########
fe/fe-core/src/main/java/org/apache/doris/statistics/AnalysisManager.java:
##########
@@ -157,6 +158,11 @@ public AnalysisManager() {
this.taskExecutor = new
AnalysisTaskExecutor(Config.statistics_simultaneously_running_task_num,
Integer.MAX_VALUE);
this.statisticsCache = new StatisticsCache();
+ this.dropStatsExecutors = ThreadPoolManager.newDaemonThreadPool(
+ 1, 1, 0,
+ TimeUnit.DAYS, new LinkedBlockingQueue<>(10),
Review Comment:
I think 10 is enough. Truncate table operation is usually not very
frequently and not very heavy unless it's a table with many partitions and
columns. When the queue is full, new request will simply aborted. It's not big
problem. The only impact is the cached stats will not be invalidated after
truncate operation, but after truncating, the table is not heathy anymore, it
will be auto analyzed next time and the cache will be updated after that.
--
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: commits-unsubscr...@doris.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
