In a Starrocks 3.5 shared data cluster I had to dr...
# questions-and-troubleshooting
j
In a Starrocks 3.5 shared data cluster I had to drop the
_statistics_
database due to lingering effects from moving my storage blob. It appears to have recreated all of the tables in the new
_statistics_
database except for the
pipe_file_list
table, now I'm seeing a bunch of errors in the logs like
Copy code
2025-11-24 19:46:39.947Z ERROR (PipeScheduler|61) [SimpleExecutor.executeDQL():103] RepoExecutor execute SQL failed SELECT `pipe_id`, `file_name`, `file_version`, `file_size`, `state`, `last_modified`, `staged_time`, `start_load`, `finish_load`, `error_info`, `insert_label` FROM _statistics_.pipe_file_list WHERE `pipe_id` = 19867582 AND `state` = 'UNLOADED' LIMIT 256
com.starrocks.sql.analyzer.SemanticException: Getting analyzing error. Detail message: Unknown table '_statistics_.pipe_file_list'.
  at com.starrocks.sql.analyzer.QueryAnalyzer.resolveTable(QueryAnalyzer.java:1524)
  at com.starrocks.sql.analyzer.QueryAnalyzer$Visitor.resolveTableRef(QueryAnalyzer.java:552)
  at com.starrocks.sql.analyzer.QueryAnalyzer$Visitor.visitSelect(QueryAnalyzer.java:366)
  at com.starrocks.sql.analyzer.QueryAnalyzer$Visitor.visitSelect(QueryAnalyzer.java:286)
  at com.starrocks.sql.ast.SelectRelation.accept(SelectRelation.java:232)
  at com.starrocks.sql.analyzer.QueryAnalyzer$Visitor.process(QueryAnalyzer.java:291)
  at com.starrocks.sql.analyzer.QueryAnalyzer$Visitor.visitQueryRelation(QueryAnalyzer.java:306)
  at com.starrocks.sql.analyzer.QueryAnalyzer$Visitor.visitQueryStatement(QueryAnalyzer.java:296)
  at com.starrocks.sql.analyzer.QueryAnalyzer$Visitor.visitQueryStatement(QueryAnalyzer.java:286)
  at com.starrocks.sql.ast.QueryStatement.accept(QueryStatement.java:72)
  at com.starrocks.sql.analyzer.QueryAnalyzer$Visitor.process(QueryAnalyzer.java:291)
  at com.starrocks.sql.analyzer.QueryAnalyzer.analyze(QueryAnalyzer.java:124)
  at com.starrocks.sql.analyzer.Analyzer$AnalyzerVisitor.visitQueryStatement(Analyzer.java:467)
  at com.starrocks.sql.analyzer.Analyzer$AnalyzerVisitor.visitQueryStatement(Analyzer.java:189)
  at com.starrocks.sql.ast.QueryStatement.accept(QueryStatement.java:72)
  at com.starrocks.sql.ast.AstVisitor.visit(AstVisitor.java:100)
  at com.starrocks.sql.analyzer.Analyzer.analyze(Analyzer.java:186)
Is this an actual problem and is there a way to fix this?
m
once the fe restart, it would recreate this table