Welcome! Please see the About page for a little more info on how this works.

+1 vote
in Analytics by
edited by

I'm having trouble configuring analytics support. I have upgraded the instance type of the access gateway and synced the configuration.

After restarting the gateway, I see log entries like:

  [2020-11-20T11:12:05+02:00] (analytics-launcher-i-0d55456c7d45d2f92) Starting presto- server
  [2020-11-20T11:12:05+02:00] (analytics-launcher-i-0d55456c7d45d2f92) java_props: -Dnode.id=ab602e6a-f4b7-47fc-840d-79cf355f6374 -Ddatomic.client.config='{:server-type :cloud      :region "eu-central-1"      :system "redacted"      :endpoint "http://entry.redacted.eu-central-1.datomic.net:8182"}'
  [2020-11-20T11:12:05+02:00] (analytics-launcher-i-0d55456c7d45d2f92) presto_props --etc-dir=/opt/presto-etc   --node-config=/opt/presto-config/node.properties   --jvm-config=/opt/presto-config/jvm.config   --config=/opt/presto-config/config.properties
  [2020-11-20T11:12:06+02:00] (analytics-launcher-i-0d55456c7d45d2f92) Started as 18945
  [2020-11-20T11:12:12+02:00] (analytics-launcher-i-0d55456c7d45d2f92) Exception in thread 
  "main" java.lang.IllegalArgumentException: Cannot parse version
	at io.prestosql.server.JavaVersion.parse(JavaVersion.java:76)
	at io.prestosql.server.PrestoSystemRequirements.verifyJavaVersion(PrestoSystemRequirements.java:98)
	at io.prestosql.server.PrestoSystemRequirements.verifyJvmRequirements(PrestoSystemRequirements.java:44)
	at io.prestosql.server.PrestoServer.run(PrestoServer.java:90)
	at io.prestosql.$gen.Presto_329____20201120_091206_1.run(Unknown Source)
	at io.prestosql.server.PrestoServer.main(PrestoServer.java:72)

It seems the offending code has been changed in presto https://github.com/prestosql/presto/commit/e7eeeedcc9751c022ffb9df648ee5442cd421c32

My compute group / access gateway is running the latest datomic release 715.

1 Answer

+1 vote
selected by
Best answer

Hi Tatu,

We are aware of the issue and it was caused by the auto-upgrade security update that installed a new version of Java on these machines. We are working to ship the updated release of Presto as quickly as we can this weekend. I will update this thread when it is out the door.

In the interim, a workaround is to log onto the gateway instance and run:

sudo yum downgrade java-11-amazon-corretto java-11-amazon-corretto-headless

This will allow the presto server to restart itself which it currently cannot do.


We have released a fix for this issue with an upgrade presto version in Datomic Cloud 732-8992.  https://s3.amazonaws.com/datomic-cloud-1/cft/732-8992/datomic-solo-compute-732-8992.json