presto-admin | A tool to install , configure and manage Presto installations

by prestodb Python Version: 2.5 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | presto-admin Summary

presto-admin is a Python library typically used in Big Data, Ubuntu, Hadoop applications. presto-admin has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

A tool to install, configure and manage Presto installations

Support

Quality

Security

License

Reuse

Support

presto-admin has a low active ecosystem.

It has 170 star(s) with 102 fork(s). There are 35 watchers for this library.

It had no major release in the last 12 months.

There are 51 open issues and 28 have been closed. On average issues are closed in 84 days. There are 12 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of presto-admin is 2.5

Quality

presto-admin has 0 bugs and 0 code smells.

Security

presto-admin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

presto-admin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

presto-admin is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

presto-admin releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed presto-admin and discovered the below as its top functions. This is intended to give you an instant insight into presto-admin implemented functionality, and help decide if they suit your requirements.

Parse command line options
Update the environment
Handle generic set env variables
Returns the config callback for the given commands
Install a rpm
Get the path to the rpm rpm
Check if the RPM is corrupted
Return the latest rpm to use
Upgrade the RPM file
Add a jar to the plugin
Returns a list of all available versions
Return a copy of the presto environment
Log exception
Set environment variables from conf dict
Return the leader configuration
Configure worker configuration
Set coordinator configuration
Uninstall the rpm package
Restart the server
Validate the configuration
Uninstall package
Run tasks
Show configuration information
Return the exit code of the task
Collects the external ip of the node
Upgrade the package

Get all kandi verified functions for this library.

presto-admin Key Features

No Key Features are available at this moment for presto-admin.

presto-admin Examples and Code Snippets

No Code Snippets are available at this moment for presto-admin.

Community Discussions

Trending Discussions on presto-admin

Presto + query.max-memory-per-node configuration

How do I install presto-admin on Dataproc cluster on GCP?

QUESTION

Presto + query.max-memory-per-node configuration

Asked 2019-Sep-10 at 05:00

We not configured in our presto workers the parameter - query.max-memory-per-node

From the log seems that the value for query.max-memory-per-node is set automatically

...

ANSWER

Answered 2019-Aug-08 at 18:17

The default for query.max-memory-per-node is 10% of the available heap memory. The default for this property is set here:

https://github.com/prestosql/presto/blob/master/presto-main/src/main/java/io/prestosql/memory/NodeMemoryConfig.java#L35

IIRC we set the default value so you could have a few large queries running in a cluster. The exact number isn't clear from this value alone. If you take a look at the configurations in the file linked above you will see that the system first reserves 30% of the heap for "unaccounted memory allocations", because Presto doesn't track all allocations. Then the query.max-memory-per-node is only a limit on "user" memory, which is memory controllable by the query author such as group by and join hash tables. This value does not include input and output buffers which are automatically managed by Presto.

With all of that put together, I would expect with the default values you can run 3-5 large queries concurrently on the code.

As for how you want to set these, it really depends on your workload. If you expect to have a large mixed workload, the defaults may work for you. If you want to be able to dedicate the entire cluster to a single worker, you can increase the values to near the heap size (make sure to leave head room for untracked allocations).

Source https://stackoverflow.com/questions/57418276

QUESTION

How do I install presto-admin on Dataproc cluster on GCP?

Asked 2019-Mar-15 at 20:12

I started my cluster as follows:

...

ANSWER

Answered 2018-Sep-05 at 12:12

This did it for me.

Source https://stackoverflow.com/questions/51450727

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install presto-admin

You can download it from GitHub.
You can use presto-admin like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: