QueryGrid 2.0 - EMR configuration issues

Presto
Teradata Employee

Re: QueryGrid 2.0 - EMR configuration issues

Yes, I did use presto admin, it's was part of the installation process. I did encounter some small issues that I solved. For example, when trying to change the presto port (port 8080 was taken)... it didn't work for me and I had to restart the cluster. Will send you the output, just send me an email to igor.machin@teradata.com and I will respond with the log attached. I was able to start presto and run commands with the cli.

Thanks for your help.

Teradata Employee

Re: QueryGrid 2.0 - EMR configuration issues

Output from ./presto-admin server status (actually on AWS EC2 the command is sudo ./presto-admin -i ../presto_cluster.pem server status as you have to put the pem file and do everything with sudo):

 

Server Status:
0.0.0.0(IP: 172.31.60.6, Roles: coordinator, worker): Running
Node URI(http): http://172.31.60.6:8080
Presto Version: 0.167-t.0.2
Node status: active
Catalogs: system, tpch

Teradata Employee

Re: QueryGrid 2.0 - EMR configuration issues

The output looks good from the Presto 167t perspective. I presume you are able to use Presto CLI and run some basic queries: "SELECT COUNT(*) FROM tpch.sf1.nation" for example.

To access data in S3 you will need to configure the Hive connector as described in our docs.

 

Going back to your initial QueryGrid-related question, please reach out to the support organization of that product.

 

Teradata Employee

Re: QueryGrid 2.0 - EMR configuration issues

Output as per your request:

 

[ec2-user@ip-172-31-60-6 prestoadmin]$ presto
presto> SELECT COUNT(*) FROM tpch.sf1.nation
-> ;
_col0
-------
25
(1 row)

Query 20170522_172201_00013_yr3em, FINISHED, 1 node
Splits: 21 total, 21 done (100.00%)
0:00 [25 rows, 0B] [213 rows/s, 0B/s]

presto>