Can't run Snowflake query (SQL) in Datalore Enterprise

Problems and bugs
1

I’ve installed Datalore Enterprise 2023.2 on AWS - Amazon Linux 2 on a 2-vcpu 8-GB VM. Connected, installed licence, set up and tested Snowflake connection - all good.

A simple query ‘select * from il.account limit 10;’ that takes less than a second via Snowsight fails - I’m getting three errors:

  1. Some changes were not acknowledged by the server. We’re probably experiencing technical issues.
  2. Your computation seems to be stopped. Reload the page if you want to restart it.
  3. Failed to run cells

Any help gratefully received.

2

I’m getting the following warnings and errors:

egrep ‘WARN|ERROR’ current/log/docker-compose-up.log
docker-compose-datalore-1 | WARN : Forking second JVM due to forking module(s): [logging-jul-capture]. Use --dry-run to generate the command line to avoid forking.
docker-compose-datalore-1 | 07:50:57.853 WARN [qtp1653844940-18] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 17405ms:
docker-compose-datalore-1 | 07:50:57.897 WARN [qtp1653844940-18] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 17455ms:
docker-compose-datalore-1 | 07:51:02.895 WARN [qtp1653844940-18] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 22451ms:
docker-compose-datalore-1 | 07:51:07.865 WARN [qtp1653844940-18] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 27423ms:
docker-compose-datalore-1 | 07:51:12.864 WARN [qtp1653844940-18] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 32420ms:
docker-compose-datalore-1 | 07:51:13.424 WARN [Datalore EDT Manager] j.d.n.s.c.a.impl.pool.AgentPool Failed to create single instance
docker-compose-datalore-1 | 07:51:13.435 ERROR [Datalore EDT Manager] j.d.n.s.c.a.impl.InstanceProviderImpl Failed to serve agent request for WSDf3efDWS14dezbFEBCTd/dfvNxfl0zYMw8AybEvmdh5, computation id P0FLKyi5fDketYVse4DeKo
docker-compose-datalore-1 | 07:51:13.444 WARN [Datalore EDT Manager] j.d.n.s.c.r.ConnectionManagerBasedAgentChannelProvider Failed to recover agent for computation P0FLKyi5fDketYVse4DeKo
docker-compose-datalore-1 | 07:51:13.523 WARN [Datalore EDT Manager] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 33081ms:
docker-compose-datalore-1 | 07:51:13.527 WARN [Datalore EDT Manager] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 33086ms:
docker-compose-datalore-1 | 07:51:13.571 ERROR [Datalore EDT Manager] j.d.n.s.c.e.b.PlanStateComputationResourcesMonitor Unexpected token release for YWBUGt4A6qwWMhqwOjNSuB: this token is not registered in ResourcesMonitor
docker-compose-datalore-1 | 07:51:27.858 WARN [qtp1653844940-19] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 14234ms:
docker-compose-datalore-1 | 07:51:32.860 WARN [qtp1653844940-19] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 19235ms:
docker-compose-datalore-1 | 07:51:37.858 WARN [qtp1653844940-19] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 24234ms:
docker-compose-datalore-1 | 07:51:42.864 WARN [qtp1653844940-21] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 29240ms:
docker-compose-datalore-1 | 07:51:47.861 WARN [qtp1653844940-19] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 34236ms:
docker-compose-datalore-1 | 07:51:49.751 WARN [Datalore EDT Manager] j.d.n.s.c.a.impl.pool.AgentPool Failed to create single instance
docker-compose-datalore-1 | 07:51:49.752 ERROR [Datalore EDT Manager] j.d.n.s.c.a.impl.InstanceProviderImpl Failed to serve agent request for WSDf3efDWS14dezbFEBCTd/dfvNxfl0zYMw8AybEvmdh5, computation id tNhJYZdJniXEPJT6aWnJza
docker-compose-datalore-1 | 07:51:49.754 WARN [Datalore EDT Manager] j.d.base.jvm.edt.ExecutorEdtManager Task for edt (Datalore EDT Manager) is executing 36130ms:
docker-compose-datalore-1 | 07:51:49.764 WARN [Datalore EDT Manager] j.d.n.s.c.c.ComputationControllerImpl Computation creation failed for: NOTEBOOK session X9HToNJnbNyLzasROhxgJ9 owned by WSDf3efDWS14dezbFEBCTd [with source WSDf3efDWS14dezbFEBCTd/dfvNxfl0zYMw8AybEvmdh5]
docker-compose-datalore-1 | 07:51:49.769 ERROR [Datalore EDT Manager] j.d.n.s.c.c.ComputationControllersCollection Failed to start computation P0FLKyi5fDketYVse4DeKo for session NOTEBOOK session X9HToNJnbNyLzasROhxgJ9 owned by WSDf3efDWS14dezbFEBCTd [with source WSDf3efDWS14dezbFEBCTd/dfvNxfl0zYMw8AybEvmdh5]
docker-compose-datalore-1 | 07:51:49.774 ERROR [Datalore EDT Manager] j.d.n.s.c.e.b.PlanStateComputationResourcesMonitor Unexpected token release for mkGaVVdnsXRW6X3N84pRuG: this token is not registered in ResourcesMonitor

3

OK - there was another error hiding in the logs (Java stack traces - I haven’t missed you!). Something along the lines of “error … no space left on device”. And yes, /var/lib/docker was full.

A couple of thoughts on additions to the ‘prerequisites’ part of the installation guide:

  • Disk - docker will need lots for the /var/lib/docker - 20G and I’ve only run one query
  • x64 - I’m sure most people default to that, but I tried ARM because of a misleading ‘docker compose’ release-notes page (latest version doesn’t support Linux-x64 at time of writing)

So now I’m up and running, Snowflake queries working. Time to dig deeper.