You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The S3 connection seems to timeout... Is there a config that I can change? It's maybe the 3 wildcards (*) that make the scanning very slow ? As when I created a pipe to ingest from another prefix with only 2 wildcards (no filename column) it worked, even with slight more files.
The S3 connection seems to timeout... Is there a config that I can change? It's maybe the 3 wildcards (*) that make the scanning very slow ? As when I created a pipe to ingest from another prefix with only 2 wildcards (no filename column) it worked, even with slight more files.
Steps to reproduce the behavior (Required)
Expected behavior (Required)
Successful creation of pipe;
Real behavior (Required)
Access storage error. Error message: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3e5549aa[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@be02396[Wrapped task = software.amazon.awssdk.core.internal.http.timers.SyncTimeoutTask@2c529256]] rejected from java.util.concurrent.ScheduledThreadPoolExecutor@1a12c692[Shutting down, pool size = 5, active threads = 0, queued tasks = 2, completed tasks = 36172]
Sometimes when I retry I also get this error:
Access storage error. Error message: `s3://BUCKET': FileSystem is closed!
Note that I am using starrocks in shared data mode and the same bucket is used to store the parquet files to load and the data of the cluster.
StarRocks version (Required)
select current_version()
3.3.0-19a3f66
The text was updated successfully, but these errors were encountered: