Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update documentation, distributed (cluster) mode deployment #46

Closed
3 tasks done
zhenik opened this issue Oct 20, 2020 · 4 comments · Fixed by #79
Closed
3 tasks done

Update documentation, distributed (cluster) mode deployment #46

zhenik opened this issue Oct 20, 2020 · 4 comments · Fixed by #79

Comments

@zhenik
Copy link
Contributor

zhenik commented Oct 20, 2020

What is the issue?

Ref: https://github.com/fredrikhgrelland/terraform-nomad-presto#option-2-presto-and-nomad

Verifying setup -> Option 2 does not work when deploying presto in distributed mode.
It fails on the step when the user needs to execute a command

show catalogs;

After command presto

Suggestion(s)/solution(s) [Optional]

Check the configuration of coordinator.

  • It might be the wrong port 8080, due to internal proxy communication
  • http disabled, only https
node.id=3b1c9ca0-2096-9018-22c1-017d58008f1c
node.environment=presto
node.internal-address=presto


coordinator=true
node-scheduler.include-coordinator=false
discovery-server.enabled=true
discovery.uri=https://127.0.0.1:25056

dynamic.http-client.https.hostname-verification=false
failure-detector.http-client.https.hostname-verification=false
memoryManager.http-client.https.hostname-verification=false
scheduler.http-client.https.hostname-verification=false
workerInfo.http-client.https.hostname-verification=false

discovery.http-client.https.hostname-verification=false
node-manager.http-client.https.hostname-verification=false
exchange.http-client.https.hostname-verification=false


http-server.http.enabled=false
http-server.authentication.type=CERTIFICATE
# Work behind proxy
http-server.authentication.allow-insecure-over-http=true
http-server.process-forwarded=true
http-server.https.enabled=true
http-server.https.port=25056
http-server.https.keystore.path=/local/presto.pem
http-server.https.truststore.path=/local/roots.pem

# This is the same jks, but it will not do the consul connect authorization in intra cluster communication
internal-communication.https.required=true

internal-communication.shared-secret= "asdasdsadafdsa"

internal-communication.https.keystore.path=/local/presto.pem
internal-communication.https.truststore.path=/local/roots.pem

query.client.timeout=5m
query.min-expire-age=30m
query.max-memory=76MB

Checklist (after created issue)

  • Added label(s)
  • Added to project
  • Added to milestone
@claesgill
Copy link
Contributor

I recreated this, but in my end, it seems to work. Maybe I misunderstood something?

presto

@zhenik
Copy link
Contributor Author

zhenik commented Nov 11, 2020

@claesgill you have run presto in standalone mode. This issue is relevant for distributed (cluster) mode.

Screenshot 2020-11-11 at 08 51 08

@zhenik zhenik changed the title Update documentation, distributed mode deployment Update documentation, distributed (cluster) mode deployment Nov 11, 2020
@claesgill
Copy link
Contributor

@claesgill you have run presto in standalone mode. This issue is relevant for distributed (cluster) mode.

Screenshot 2020-11-11 at 08 51 08

Option 2 specify use of standalone...

@zhenik
Copy link
Contributor Author

zhenik commented Nov 11, 2020

This section was written when there was only standalone mode. Anyway we need an update for documentation

@claesgill claesgill mentioned this issue Nov 11, 2020
5 tasks
Team DataStack automation moved this from Priortized Backlog to QA Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants