[jira] [Comment Edited] (BIGTOP-2325) Deployment recipes for HAWQ

["Konstantin Boudnik (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168045#comment-15168045 ] 

Konstantin Boudnik edited comment on BIGTOP-2325 at 2/25/16 10:56 PM:
----------------------------------------------------------------------

Deployment is sorta there. Issues:
for cluster init:
  -  files under /etc/hawq/conf/* should belong to hawq:hawq
     SSH keys :( ? I have no clue whatsoever why the ssh is needed. Ideally,
  -  binary scripts should work locally only. Any anything that requires
     ssh'ing around. needs to be done as in a wrapper around those local
     scripts.
  - looks like some Postgres parameters need to be tuned as
selecting default max_connections ... initdb: error 256 from: "/usr/lib/hawq/bin/postgres" --boot -x0 -F -c max_connections=++++1280 -c shared_buffers=4000 -c max_fsm_pages=200000 < "/dev/null" > "/var/run/hawq/hawqAdminLogs/master.initdb" 2>&1 ini++++tdb: removing contents of data directory "/var/run/hawq/hawq-data-directory/masterdd"
Master postgres initdb failed

This happens at least in a docker.

service start should use different parameters for
    - master
    - segment

Another major issue: HAWQ scripts are ssh'ing all the time for whatever is the reason. There should be a set of local-node scripts for the functionality required; and wrappers that would ssh around and call the local-node scripts. Otherwise, this crap is going to blow.


was (Author: cos):
Deployment is sorta there. Issues:
for cluster init:
  -  files under /etc/hawq/conf/* should belong to hawq:hawq
     SSH keys :( ? I have no clue whatsoever why the ssh is needed. Ideally,
  -  binary scripts should work locally only. Any anything that requires
     ssh'ing around. needs to be done as in a wrapper around those local
     scripts.
  - looks like some Postgres parameters need to be tuned as
selecting default max_connections ... initdb: error 256 from: "/usr/lib/hawq/bin/postgres" --boot -x0 -F -c max_connections=++++1280 -c shared_buffers=4000 -c max_fsm_pages=200000 < "/dev/null" > "/var/run/hawq/hawqAdminLogs/master.initdb" 2>&1 ini++++tdb: removing contents of data directory "/var/run/hawq/hawq-data-directory/masterdd"
Master postgres initdb failed

This happens at least in a docker.

service start should use different parameters for
    - master
    - segment


> Deployment recipes for HAWQ
> ---------------------------
>
>                 Key: BIGTOP-2325
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2325
>             Project: Bigtop
>          Issue Type: Sub-task
>          Components: deployment
>    Affects Versions: 1.1.0
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>             Fix For: 1.2.0
>
>         Attachments: 0003-BIGTOP-2325.-Deployment-recipes-for-HAWQ.patch
>
>
> Puppet recipes for HAWQ are required for automatic deployment and configuration



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)