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

Lin Wen commented on HAWQ-1318:
-------------------------------

The reason is Resource manager process is going to update 
gp_segment_configuration table, but the acl check("user":"superuser", 
"database": "template1", "schema": ""public" , "privileges":  "usage")on this 
request is sent to ranger check, since the configuration of RPS is wrong, hawq 
master cann't connect RPS. so RM process failed in updating catalog table. 
The solution is for superuser 's access to PUBLIC should check natively, not 
via ranger. 

> Can't start/stop master succesfully if ranger is enable and with a wrong RPS 
> address
> ------------------------------------------------------------------------------------
>
>                 Key: HAWQ-1318
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1318
>             Project: Apache HAWQ
>          Issue Type: Bug
>          Components: Security
>            Reporter: Lin Wen
>            Assignee: Lin Wen
>
> If ranger enable and with a wrong RPS address, hawq can start but can't 
> start/stop succesfully.
> Lins-MacBook-Pro:apache-hawq linw$ hawq stop cluster -a
> 20170209:10:21:51:043784 hawq_stop:Lins-MacBook-Pro:linw-[INFO]:-Prepare to 
> do 'hawq stop'
> 20170209:10:21:51:043784 hawq_stop:Lins-MacBook-Pro:linw-[INFO]:-You can find 
> log in:
> 20170209:10:21:51:043784 
> hawq_stop:Lins-MacBook-Pro:linw-[INFO]:-/Users/linw/hawqAdminLogs/hawq_stop_20170209.log
> 20170209:10:21:51:043784 hawq_stop:Lins-MacBook-Pro:linw-[INFO]:-GPHOME is 
> set to:
> 20170209:10:21:51:043784 
> hawq_stop:Lins-MacBook-Pro:linw-[INFO]:-/Users/linw/hawq-bin
> 20170209:10:21:51:043784 hawq_stop:Lins-MacBook-Pro:linw-[INFO]:-Stop hawq 
> with args: ['stop', 'cluster']
> 20170209:10:21:51:043784 hawq_stop:Lins-MacBook-Pro:linw-[INFO]:-No standby 
> host configured
> 20170209:10:21:51:043784 hawq_stop:Lins-MacBook-Pro:linw-[INFO]:-Stop hawq 
> cluster
> 20170209:10:22:22:043784 hawq_stop:Lins-MacBook-Pro:linw-[ERROR]:-Failed to 
> connect to the running database, please check master status
> 20170209:10:22:22:043784 hawq_stop:Lins-MacBook-Pro:linw-[ERROR]:-Or you can 
> check hawq stop --help for other stop options
>  501 43719     1   0 10:20AM ??         0:00.58 
> /Users/linw/hawq-bin/bin/postgres -D /Users/linw/hawq-data/masterdd -i -M 
> master -p 5432 --silent-mode=true
>   501 43721 43719   0 10:20AM ??         0:00.02 postgres: port  5432, master 
> logger process
>   501 43724 43719   0 10:20AM ??         0:00.01 postgres: port  5432, stats 
> collector process
>   501 43725 43719   0 10:20AM ??         0:00.07 postgres: port  5432, writer 
> process
>   501 43726 43719   0 10:20AM ??         0:00.01 postgres: port  5432, 
> checkpoint process
>   501 43727 43719   0 10:20AM ??         0:00.01 postgres: port  5432, 
> seqserver process
>   501 43728 43719   0 10:20AM ??         0:00.01 postgres: port  5432, WAL 
> Send Server process
>   501 43729 43719   0 10:20AM ??         0:00.00 postgres: port  5432, DFS 
> Metadata Cache process
>   501 43743     1   0 10:20AM ??         0:00.79 
> /Users/linw/hawq-bin/bin/postgres -D /Users/linw/hawq-data/segmentdd -i -M 
> segment -p 40000 --silent-mode=true
>   501 43744 43743   0 10:20AM ??         0:00.02 postgres: port 40000, logger 
> process
>   501 43747 43743   0 10:20AM ??         0:00.01 postgres: port 40000, stats 
> collector process
>   501 43748 43743   0 10:20AM ??         0:00.07 postgres: port 40000, writer 
> process
>   501 43749 43743   0 10:20AM ??         0:00.01 postgres: port 40000, 
> checkpoint process
>   501 43750 43743   0 10:20AM ??         0:00.16 postgres: port 40000, 
> segment resource manager
>   501 43830 43719   0 10:22AM ??         0:00.01 postgres: port  5432, master 
> resource manager
>   501 43867 43719   0 10:24AM ??         0:00.01 postgres: port  5432, linw 
> template1 [local] cmd1 SELECT [local]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to