-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
[Discussion] Do we have presto native worker deployment guide? #21242
Comments
@xumingming : We do not. There is some experience related to production deployments at Meta, Bytedance that will be presented at PrestoCon Dec 2023. We can consolidate the presentations to a writeup for the github/site. Would be great if you could outline more specific questions you have about deployment (here or in other issues), and we can consolidate those as well. |
@aditi-pandit Do not have very specific questions now, was hoping there is a simple step-by-step doc I can follow to setup a presto native worker cluster for future test like perf test. |
@xumingming : You can start with setting up a native worker cluster using docker-compose from https://github.com/prestodb/prestorials/tree/main/docker-compose-native |
@aditi-pandit Thanks, I will give it a try. |
@aditi-pandit I have specific questions now :( I didn't fully follow the docker compose guide(https://github.com/prestodb/prestorials/tree/main/docker-compose-native), but the docker compose guide & the development guide did give me some hints, I have done the following:
The native worker seems started successfully, because I saw the following in stdout:
But from Presto UI, the worker count does not include the native worker, there is only one worker(the java coordinator itself.), What could be the problem? |
No response and not a big deal, closing it. |
I know there is a DEVELOPMENT guide for presto native worker(https://github.com/prestodb/presto/tree/master/presto-native-execution), do we have DEPLOYMENT guide for deploying presto native worker in linux production environment?
The text was updated successfully, but these errors were encountered: