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

Debian support for Presto Plugin #27

Open
allanwilson opened this issue Apr 23, 2017 · 1 comment
Open

Debian support for Presto Plugin #27

allanwilson opened this issue Apr 23, 2017 · 1 comment

Comments

@allanwilson
Copy link

Installed Presto plugin for Ambari 2.4.2 on Debian 7.
Running ambari as a non-root ambari user.
Ambari user has all required sudo privs per Hortonworks Install Documentation for Ambari 2.4.2

Setting up the Presto service failed on these two steps:

  1. mkdir /usr/lib/presto and required subdirs
    Worked around the above issue by manually creating the directories and setting ownership to the user ambari.

Most likely this is a support issue for Ambari running as non root. The install would've worked at this stage if the script issued a sudo in front of the mkdir commands (most likely).

  1. Service install via Ambari failed installing Presto software
    Trying to install an rpm package 'presto-server-rpm-0.161.rpm' from /tmp. This is a Debian platform, so naturally this failed. Any support for Debian coming up?

I'll try installing the Presto software manually on our datanodes and see if that works.

Thanks

Allan Wilson

@petroav
Copy link
Contributor

petroav commented Apr 24, 2017

Any support for Debian coming up?

Unfortunately, I don't think anyone is actively working on this.

You could make the plugin work with an installation of Presto from tar.gz however you'll have to hack quite a few things. The RPM lays out start and stop scripts in /etc/init.d/ whereas the tar.gz doesn't. You'll have to edit the scripts in this repo's package/scripts directory. There are also probably other inconsistencies (that I can't remember now off the top of my head) between the two types of installations that will make this difficult. Also if you're editing the scripts live on a multinode cluster you'll have to delete the cached versions of the scripts on the worker nodes where the Ambari python agent is running so that your new versions get picked up.

Hope this helps!

@petroav petroav closed this as completed Apr 24, 2017
@petroav petroav reopened this Apr 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants