@fuliu This means that when the query started to execute, the first step is to assign work fragments to different executor cores. When you get the above error, it means executor is not available. Are you able to check in the executor logs if the executor was up when the query started?
@balaji.ramaswamy I added the jvm parameter -Dio.netty.tryReflectionSetAccessible=true, and now I can query the data. How can the executor logs you mentioned be printed on the idea console? I have tried some configurations but they cannot take effect. Can you give me some guidance?
Attached is the IDEA startup log. You see that no info level log is printed.
Since you are running Dremio through intelij as a developer, I can share my run configuration which I use for day to day development:
-Dpaths.local=/Users/bennychow/dev/dremioData/data
-Dpaths.dist="file:///Users/bennychow/dev/dremioData/pdfs"
-Ddremio.log.path=/Users/bennychow/dev/dremioData/log
-Dlogback.configurationFile=/Users/bennychow/dev/dremioData/conf/logback.xml
-Dservices.coordinator.auto-upgrade=true
-Ddremio.telemetry.configfile=/Users/bennychow/dev/dremioData/conf/dremio-telemetry.yaml
-Ddremio_allowTestApis=true
-Ddebug.allowNewerKVStore=true
-Dcom.sun.management.jmxremote.port=1099
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Dio.netty.tryReflectionSetAccessible=true
-Dservices.coordinator.command-pool.size=20
More info here: Configuring via dremio.conf | Dremio Documentation
logback.xml.zip (1.8 KB)
I used the system’s logbak configuration file, but no log file was generated in the log path. Could you share your configuration file?