[jira] [Updated] (HAWQ-1343) Travis build fails due to pip command not found

2017-02-17 Thread Ed Espino (JIRA)

 [ 
https://issues.apache.org/jira/browse/HAWQ-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino updated HAWQ-1343:

Fix Version/s: (was: 2.1.0.0-incubating)
   2.2.0.0-incubating

> Travis build fails due to pip command not found
> ---
>
> Key: HAWQ-1343
> URL: https://issues.apache.org/jira/browse/HAWQ-1343
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Build
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.2.0.0-incubating
>
>
> The Travis CI OS X image is changing in unexpected ways.  The latest being a 
> missing "pip" command . This change will install it with the following:
> {code}
> sudo easy_install pip
> {code}



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


[jira] [Resolved] (HAWQ-1134) Add Bigtop layout specific pxf-private classpath

2017-02-17 Thread Ed Espino (JIRA)

 [ 
https://issues.apache.org/jira/browse/HAWQ-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino resolved HAWQ-1134.
-
Resolution: Fixed

Roman merged to master.

> Add Bigtop layout specific pxf-private classpath
> 
>
> Key: HAWQ-1134
> URL: https://issues.apache.org/jira/browse/HAWQ-1134
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: PXF
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.1.0.0-incubating
>
>
> Currently PXF ships with HDP and PHD specific classpath files. It would be 
> great to have Bigtop specific one.



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


[GitHub] incubator-hawq issue #1133: HAWQ-1344. Rollback Apache HAWQ version to 2.1.0...

2017-02-17 Thread edespino
Github user edespino commented on the issue:

https://github.com/apache/incubator-hawq/pull/1133
  
The Apache RAT pom.xml file (root directory) needs to be updated as well: 
"2.2" --> "2.1"


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Updated] (HAWQ-1344) Rollback Apache HAWQ version to 2.1.0.0

2017-02-17 Thread Shivram Mani (JIRA)

 [ 
https://issues.apache.org/jira/browse/HAWQ-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shivram Mani updated HAWQ-1344:
---
Description: 
Apache HAWQ version which was set to 2.2.0.0 will now move back to its original 
2.1.0.0 version
Set PXF version to 3.2

  was:Apache HAWQ version which was set to 2.2.0.0 will now move back to its 
original 2.1.0.0 version


> Rollback Apache HAWQ version to 2.1.0.0
> ---
>
> Key: HAWQ-1344
> URL: https://issues.apache.org/jira/browse/HAWQ-1344
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build
>Reporter: Shivram Mani
>Assignee: Shivram Mani
> Fix For: 2.2.0.0-incubating
>
>
> Apache HAWQ version which was set to 2.2.0.0 will now move back to its 
> original 2.1.0.0 version
> Set PXF version to 3.2



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


[jira] [Assigned] (HAWQ-1344) Rollback Apache HAWQ version to 2.1.0.0

2017-02-17 Thread Shivram Mani (JIRA)

 [ 
https://issues.apache.org/jira/browse/HAWQ-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shivram Mani reassigned HAWQ-1344:
--

Assignee: Shivram Mani  (was: Ed Espino)

> Rollback Apache HAWQ version to 2.1.0.0
> ---
>
> Key: HAWQ-1344
> URL: https://issues.apache.org/jira/browse/HAWQ-1344
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build
>Reporter: Shivram Mani
>Assignee: Shivram Mani
> Fix For: 2.2.0.0-incubating
>
>
> Apache HAWQ version which was set to 2.2.0.0 will now move back to its 
> original 2.1.0.0 version



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


[GitHub] incubator-hawq pull request #1114: HAWQ-1320. Remove reference to PXF rpm ve...

2017-02-17 Thread shivzone
Github user shivzone closed the pull request at:

https://github.com/apache/incubator-hawq/pull/1114


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Created] (HAWQ-1344) Rollback Apache HAWQ versino to 2.1.0.0

2017-02-17 Thread Shivram Mani (JIRA)
Shivram Mani created HAWQ-1344:
--

 Summary: Rollback Apache HAWQ versino to 2.1.0.0
 Key: HAWQ-1344
 URL: https://issues.apache.org/jira/browse/HAWQ-1344
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Build
Reporter: Shivram Mani
Assignee: Ed Espino
 Fix For: 2.2.0.0-incubating


Apache HAWQ version which was set to 2.2.0.0 will now move back to its original 
2.1.0.0 version



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


[GitHub] incubator-hawq issue #1132: HAWQ-1343. - Install pip and minor formatting ch...

2017-02-17 Thread ljainpivotalio
Github user ljainpivotalio commented on the issue:

https://github.com/apache/incubator-hawq/pull/1132
  
brew install python


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (HAWQ-1343) Travis build fails due to pip command not found

2017-02-17 Thread Lav Jain (JIRA)

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

Lav Jain commented on HAWQ-1343:


brew install python should install pip automatically.

> Travis build fails due to pip command not found
> ---
>
> Key: HAWQ-1343
> URL: https://issues.apache.org/jira/browse/HAWQ-1343
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Build
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.2.0.0-incubating
>
>
> The Travis CI OS X image is changing in unexpected ways.  The latest being a 
> missing "pip" command . This change will install it with the following:
> {code}
> sudo easy_install pip
> {code}



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


[GitHub] incubator-hawq pull request #1131: HAWQ-1322 Changed RPS RPM name to hawq-ra...

2017-02-17 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/incubator-hawq/pull/1131


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Resolved] (HAWQ-1332) Can not grant database and schema privileges without table privileges in ranger or ranger plugin service

2017-02-17 Thread Alexander Denissov (JIRA)

 [ 
https://issues.apache.org/jira/browse/HAWQ-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Denissov resolved HAWQ-1332.
--
   Resolution: Not A Problem
Fix Version/s: 2.3.0.0-incubating

> Can not grant database and schema privileges without table privileges in 
> ranger or ranger plugin service
> 
>
> Key: HAWQ-1332
> URL: https://issues.apache.org/jira/browse/HAWQ-1332
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Security
>Reporter: Chunling Wang
>Assignee: Alexander Denissov
> Fix For: 2.3.0.0-incubating
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> We try to grant database connect and schema usage privileges to a non-super 
> user to connect database. We find that if we set policy with database and 
> schema included, but with table excluded, we can not connect database. But if 
> we include table, we can connect to database. We think there may be bug in 
> Ranger Plugin Service or Ranger. Here are steps to reproduce it.
> 1. create a new user "usertest1" in database:
> {code}
> $ psql postgres
> psql (8.2.15)
> Type "help" for help.
> postgres=# CREATE USER usertest1;
> NOTICE:  resource queue required -- using default resource queue "pg_default"
> CREATE ROLE
> postgres=#
> {code}
> 2. add user "usertest1" in pg_hba.conf
> {code}
> local all usertest1 trust
> {code}
> 3. set policy with database and schema included, with table excluded
> !screenshot-1.png|width=800,height=400!
> 4. connect database with user "usertest1" but failed with permission denied
> {code}
> $ psql postgres -U usertest1
> psql: FATAL:  permission denied for database "postgres"
> DETAIL:  User does not have CONNECT privilege.
> {code}
> 5. set policy with database, schema and table included
> !screenshot-2.png|width=800,height=400!
> 6. connect database with user "usertest1" and succeed
> {code}
> $ psql postgres -U usertest1
> psql (8.2.15)
> Type "help" for help.
> postgres=#
> {code}
> But if we do not set table as "*", and specify table like "a", we can not 
> access database either.
> !screenshot-3.png|width=800,height=400!



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


[GitHub] incubator-hawq issue #720: HAWQ-823. Initial Amazon S3 External Table Suppor...

2017-02-17 Thread edespino
Github user edespino commented on the issue:

https://github.com/apache/incubator-hawq/pull/720
  
@vVineet ... as this work is on hold, can we close this PR and revive at a 
later point in time?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-hawq pull request #993: HAWQ-1134. Add Bigtop layout specific pxf-...

2017-02-17 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/incubator-hawq/pull/993


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Updated] (HAWQ-1134) Add Bigtop layout specific pxf-private classpath

2017-02-17 Thread Ed Espino (JIRA)

 [ 
https://issues.apache.org/jira/browse/HAWQ-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino updated HAWQ-1134:

Fix Version/s: 2.2.0.0-incubating

> Add Bigtop layout specific pxf-private classpath
> 
>
> Key: HAWQ-1134
> URL: https://issues.apache.org/jira/browse/HAWQ-1134
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: PXF
>Reporter: Roman Shaposhnik
>Assignee: Roman Shaposhnik
> Fix For: 2.2.0.0-incubating
>
>
> Currently PXF ships with HDP and PHD specific classpath files. It would be 
> great to have Bigtop specific one.



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


[GitHub] incubator-hawq pull request #1132: HAWQ-1343. - Install pip and minor format...

2017-02-17 Thread edespino
GitHub user edespino opened a pull request:

https://github.com/apache/incubator-hawq/pull/1132

HAWQ-1343. - Install pip and minor formatting change.

The latest Travis CI OS X builds are failing 
(https://travis-ci.org/apache/incubator-hawq/builds/202425654) because "pip" 
command is not found.  This change will install it.

Error:
$ sudo pip install pycrypto
sudo: pip: command not found

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/edespino/incubator-hawq HAWQ-1343

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-hawq/pull/1132.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1132


commit ce4c7e2ed383a70cd53857023826eb3043c887a9
Author: Ed Espino 
Date:   2017-02-17T15:50:00Z

HAWQ-1343. - Install pip and minor formatting change.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Assigned] (HAWQ-1330) Add ASF license header to additional files

2017-02-17 Thread Ed Espino (JIRA)

 [ 
https://issues.apache.org/jira/browse/HAWQ-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino reassigned HAWQ-1330:
---

Assignee: Ed Espino  (was: Jiali Yao)

> Add ASF license header to additional files
> --
>
> Key: HAWQ-1330
> URL: https://issues.apache.org/jira/browse/HAWQ-1330
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Tests
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.2.0.0-incubating
>
>
> Add ASF header to the following files (pom.xml updated as well):
> {code}
> .travis.yml
> pxf/pxf-service/src/main/resources/pxf-private.classpath
> pxf/pxf-service/src/main/resources/pxf-privatehdp.classpath
> pxf/pxf-service/src/main/resources/pxf-privatephd.classpath
> pxf/pxf-service/src/main/resources/pxf-public.classpath
> src/test/amsd/Makefile
> src/test/examples/Makefile
> src/test/feature/ExternalSource/lib/Makefile
> src/test/feature/Makefile
> src/test/feature/ManagementTool/files_incomplete.yml
> src/test/feature/ManagementTool/missing_bucketnum.yml
> src/test/feature/ManagementTool/missing_checksum.yml
> src/test/feature/ManagementTool/missing_constraint_partition.yml
> src/test/feature/ManagementTool/missing_filesize.yml
> src/test/feature/ManagementTool/missing_pagesize.yml
> src/test/feature/ManagementTool/missing_rowgroupsize.yml
> src/test/feature/ManagementTool/partition/constraint_not_exists_in_catalog_tpl.yml
> src/test/feature/ManagementTool/partition/different_partition_policy_tpl.yml
> src/test/feature/ManagementTool/partition/duplicate_partition_constraint_tpl.yml
> src/test/feature/ManagementTool/partition/force_mode_normal_tpl.yml
> src/test/feature/ManagementTool/partition/sub_set_catalog_table_tpl.yml
> src/test/feature/ManagementTool/partition/table_exists_list_partition_tpl.yml
> src/test/feature/ManagementTool/partition/table_exists_range_partition_tpl.yml
> src/test/feature/ManagementTool/partition/table_exists_table_file_not_exists_tpl.yml
> src/test/feature/ManagementTool/partition/table_not_exists_list_partition_tpl.yml
> src/test/feature/ManagementTool/partition/table_not_exists_range_partition_tpl.yml
> src/test/feature/ManagementTool/partition/table_not_exists_table_file_not_exists_tpl.yml
> src/test/feature/ManagementTool/usage2_include1/includedirectory_tpl.yml
> src/test/feature/ManagementTool/usage2_include2/includedirectory_tpl.yml
> src/test/feature/ManagementTool/usage2case1/bucket0_tpl.yml
> src/test/feature/ManagementTool/usage2case1/contain_error_symbol_tpl.yml
> src/test/feature/ManagementTool/usage2case1/error_blocksize_tpl.yml
> src/test/feature/ManagementTool/usage2case1/error_checksum_tpl.yml
> src/test/feature/ManagementTool/usage2case1/error_columnnum_tpl.yml
> src/test/feature/ManagementTool/usage2case1/error_compresslevel_tpl.yml
> src/test/feature/ManagementTool/usage2case1/error_compresstype_tpl.yml
> src/test/feature/ManagementTool/usage2case1/error_encoding_tpl.yml
> src/test/feature/ManagementTool/usage2case1/error_format_tpl.yml
> src/test/feature/ManagementTool/usage2case1/error_pagesize_tpl.yml
> src/test/feature/ManagementTool/usage2case1/error_rowgroupsize_tpl.yml
> src/test/feature/ManagementTool/usage2case1/error_schema_tpl.yml
> src/test/feature/ManagementTool/usage2case1/file_under_table_directory_tpl.yml
> src/test/feature/ManagementTool/usage2case1/float_eof_tpl.yml
> src/test/feature/ManagementTool/usage2case1/includedirectory_tpl.yml
> src/test/feature/ManagementTool/usage2case1/larger_eof_tpl.yml
> src/test/feature/ManagementTool/usage2case1/minus_eof_tpl.yml
> src/test/feature/ManagementTool/usage2case1/wrong_distributed_policy_tpl.yml
> src/test/feature/ManagementTool/usage2case1/zero_eof_tpl.yml
> src/test/feature/ManagementTool/usage2case2/bucket0_tpl.yml
> src/test/feature/ManagementTool/usage2case2/contain_error_symbol_tpl.yml
> src/test/feature/ManagementTool/usage2case2/error_blocksize_tpl.yml
> src/test/feature/ManagementTool/usage2case2/error_checksum_tpl.yml
> src/test/feature/ManagementTool/usage2case2/error_columnnum_tpl.yml
> src/test/feature/ManagementTool/usage2case2/error_compresslevel_tpl.yml
> src/test/feature/ManagementTool/usage2case2/error_compresstype_tpl.yml
> src/test/feature/ManagementTool/usage2case2/error_encoding_tpl.yml
> src/test/feature/ManagementTool/usage2case2/error_format_tpl.yml
> src/test/feature/ManagementTool/usage2case2/error_pagesize_tpl.yml
> src/test/feature/ManagementTool/usage2case2/error_rowgroupsize_tpl.yml
> src/test/feature/ManagementTool/usage2case2/file_in_yaml_not_exist_tpl.yml
> src/test/feature/ManagementTool/usage2case2/file_not_included_in_yaml_config_tpl.yml
> src/test/feature/ManagementTool/usage2case2/float_eof_tpl.yml
> src/test/feature/ManagementTool/usage2case2/hash_to_random_tpl.yml
> 

[jira] [Created] (HAWQ-1343) Travis build fails due to pip command not found

2017-02-17 Thread Ed Espino (JIRA)
Ed Espino created HAWQ-1343:
---

 Summary: Travis build fails due to pip command not found
 Key: HAWQ-1343
 URL: https://issues.apache.org/jira/browse/HAWQ-1343
 Project: Apache HAWQ
  Issue Type: Task
  Components: Build
Reporter: Ed Espino
Assignee: Ed Espino
 Fix For: 2.2.0.0-incubating


The Travis CI OS X image is changing in unexpected ways.  The latest being a 
missing "pip" command . This change will install it with the following:

{code}
sudo easy_install pip
{code}



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


[GitHub] incubator-hawq issue #1131: HAWQ-1322 Changed RPS RPM name to hawq-ranger-pl...

2017-02-17 Thread zhangh43
Github user zhangh43 commented on the issue:

https://github.com/apache/incubator-hawq/pull/1131
  
+1


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Assigned] (HAWQ-1342) QE process hang in shared input scan on segment node

2017-02-17 Thread Amy (JIRA)

 [ 
https://issues.apache.org/jira/browse/HAWQ-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amy reassigned HAWQ-1342:
-

Assignee: Amy  (was: Lei Chang)

> QE process hang in shared input scan on segment node
> 
>
> Key: HAWQ-1342
> URL: https://issues.apache.org/jira/browse/HAWQ-1342
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Query Execution
>Reporter: Amy
>Assignee: Amy
> Fix For: 2.3.0.0-incubating
>
>
> QE process hang on some segment node while QD and QE on other segment nodes 
> terminated.
> {code}
> [gpadmin@test1 ~]$ cat hostfile
> test1   master   secondary namenode
> test2   segment   datanode
> test3   segment   datanode
> test4   segment   datanode
> test5   segment   namenode
> [gpadmin@test3 ~]$ ps -ef | grep postgres | grep -v grep
> gpadmin   41877  1  0 05:35 ?00:01:04 
> /usr/local/hawq_2_1_0_0/bin/postgres -D 
> /data/pulse-agent-data/HAWQ-main-FeatureTest-opt-Multinode-parallel/product/segmentdd
>  -i -M segment -p 20100 --silent-mode=true
> gpadmin   41878  41877  0 05:35 ?00:00:02 postgres: port 20100, 
> logger process
> gpadmin   41881  41877  0 05:35 ?00:00:00 postgres: port 20100, stats 
> collector process
> gpadmin   41882  41877  0 05:35 ?00:00:07 postgres: port 20100, 
> writer process
> gpadmin   41883  41877  0 05:35 ?00:00:01 postgres: port 20100, 
> checkpoint process
> gpadmin   41884  41877  0 05:35 ?00:00:11 postgres: port 20100, 
> segment resource manager
> gpadmin   42108  41877  0 05:35 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(65193) con35 seg0 cmd2 slice9 MPPEXEC 
> SELECT
> gpadmin   42416  41877  0 05:35 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(65359) con53 seg0 cmd2 slice11 MPPEXEC 
> SELECT
> gpadmin   44807  41877  0 05:36 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(2272) con183 seg0 cmd2 slice31 MPPEXEC 
> SELECT
> gpadmin   44819  41877  0 05:36 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(2278) con183 seg0 cmd2 slice10 MPPEXEC 
> SELECT
> gpadmin   44821  41877  0 05:36 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(2279) con183 seg0 cmd2 slice25 MPPEXEC 
> SELECT
> gpadmin   45447  41877  0 05:36 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(2605) con207 seg0 cmd2 slice9 MPPEXEC 
> SELECT
> gpadmin   49859  41877  0 05:38 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(4805) con432 seg0 cmd2 slice20 MPPEXEC 
> SELECT
> gpadmin   49881  41877  0 05:38 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(4816) con432 seg0 cmd2 slice7 MPPEXEC 
> SELECT
> gpadmin   51937  41877  0 05:39 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(5877) con517 seg0 cmd2 slice7 MPPEXEC 
> SELECT
> gpadmin   51939  41877  0 05:39 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(5878) con517 seg0 cmd2 slice9 MPPEXEC 
> SELECT
> gpadmin   51941  41877  0 05:39 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(5879) con517 seg0 cmd2 slice11 MPPEXEC 
> SELECT
> gpadmin   51943  41877  0 05:39 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(5880) con517 seg0 cmd2 slice13 MPPEXEC 
> SELECT
> gpadmin   51953  41877  0 05:39 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(5885) con517 seg0 cmd2 slice26 MPPEXEC 
> SELECT
> gpadmin   53436  41877  0 05:40 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(6634) con602 seg0 cmd2 slice15 MPPEXEC 
> SELECT
> gpadmin   57095  41877  0 05:41 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(8450) con782 seg0 cmd2 slice10 MPPEXEC 
> SELECT
> gpadmin   57097  41877  0 05:41 ?00:00:04 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(8451) con782 seg0 cmd2 slice11 MPPEXEC 
> SELECT
> gpadmin   63159  41877  0 05:43 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(11474) con1082 seg0 cmd2 slice15 
> MPPEXEC SELECT
> gpadmin   64018  41877  0 05:44 ?00:00:03 postgres: port 20100, 
> hawqsuperuser olap_group 10.32.35.192(11905) con1121 seg0 cmd2 slice5 MPPEXEC 
> SELECT
> {code}
> The stack info is as below and it seems that QE hang in shared input scan.
> {code}
> [gpadmin@test3 ~]$ gdb -p 42108
> (gdb) info threads
>   2 Thread 0x7f4f6b335700 (LWP 42109)  0x0032214df283 in poll () from 
> /lib64/libc.so.6
> * 1 Thread 0x7f4f9041c920 (LWP 42108)  0x0032214e1523 in select () from 
> /lib64/libc.so.6
> (gdb) 

[jira] [Created] (HAWQ-1342) QE process hang in shared input scan on segment node

2017-02-17 Thread Amy (JIRA)
Amy created HAWQ-1342:
-

 Summary: QE process hang in shared input scan on segment node
 Key: HAWQ-1342
 URL: https://issues.apache.org/jira/browse/HAWQ-1342
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Query Execution
Reporter: Amy
Assignee: Lei Chang
 Fix For: 2.3.0.0-incubating


QE process hang on some segment node while QD and QE on other segment nodes 
terminated.

{code}
[gpadmin@test1 ~]$ cat hostfile
test1   master   secondary namenode
test2   segment   datanode
test3   segment   datanode
test4   segment   datanode
test5   segment   namenode

[gpadmin@test3 ~]$ ps -ef | grep postgres | grep -v grep
gpadmin   41877  1  0 05:35 ?00:01:04 
/usr/local/hawq_2_1_0_0/bin/postgres -D 
/data/pulse-agent-data/HAWQ-main-FeatureTest-opt-Multinode-parallel/product/segmentdd
 -i -M segment -p 20100 --silent-mode=true
gpadmin   41878  41877  0 05:35 ?00:00:02 postgres: port 20100, logger 
process
gpadmin   41881  41877  0 05:35 ?00:00:00 postgres: port 20100, stats 
collector process
gpadmin   41882  41877  0 05:35 ?00:00:07 postgres: port 20100, writer 
process
gpadmin   41883  41877  0 05:35 ?00:00:01 postgres: port 20100, 
checkpoint process
gpadmin   41884  41877  0 05:35 ?00:00:11 postgres: port 20100, segment 
resource manager
gpadmin   42108  41877  0 05:35 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(65193) con35 seg0 cmd2 slice9 MPPEXEC 
SELECT
gpadmin   42416  41877  0 05:35 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(65359) con53 seg0 cmd2 slice11 MPPEXEC 
SELECT
gpadmin   44807  41877  0 05:36 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(2272) con183 seg0 cmd2 slice31 MPPEXEC 
SELECT
gpadmin   44819  41877  0 05:36 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(2278) con183 seg0 cmd2 slice10 MPPEXEC 
SELECT
gpadmin   44821  41877  0 05:36 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(2279) con183 seg0 cmd2 slice25 MPPEXEC 
SELECT
gpadmin   45447  41877  0 05:36 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(2605) con207 seg0 cmd2 slice9 MPPEXEC 
SELECT
gpadmin   49859  41877  0 05:38 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(4805) con432 seg0 cmd2 slice20 MPPEXEC 
SELECT
gpadmin   49881  41877  0 05:38 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(4816) con432 seg0 cmd2 slice7 MPPEXEC 
SELECT
gpadmin   51937  41877  0 05:39 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(5877) con517 seg0 cmd2 slice7 MPPEXEC 
SELECT
gpadmin   51939  41877  0 05:39 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(5878) con517 seg0 cmd2 slice9 MPPEXEC 
SELECT
gpadmin   51941  41877  0 05:39 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(5879) con517 seg0 cmd2 slice11 MPPEXEC 
SELECT
gpadmin   51943  41877  0 05:39 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(5880) con517 seg0 cmd2 slice13 MPPEXEC 
SELECT
gpadmin   51953  41877  0 05:39 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(5885) con517 seg0 cmd2 slice26 MPPEXEC 
SELECT
gpadmin   53436  41877  0 05:40 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(6634) con602 seg0 cmd2 slice15 MPPEXEC 
SELECT
gpadmin   57095  41877  0 05:41 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(8450) con782 seg0 cmd2 slice10 MPPEXEC 
SELECT
gpadmin   57097  41877  0 05:41 ?00:00:04 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(8451) con782 seg0 cmd2 slice11 MPPEXEC 
SELECT
gpadmin   63159  41877  0 05:43 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(11474) con1082 seg0 cmd2 slice15 MPPEXEC 
SELECT
gpadmin   64018  41877  0 05:44 ?00:00:03 postgres: port 20100, 
hawqsuperuser olap_group 10.32.35.192(11905) con1121 seg0 cmd2 slice5 MPPEXEC 
SELECT
{code}

The stack info is as below and it seems that QE hang in shared input scan.
{code}
[gpadmin@test3 ~]$ gdb -p 42108
(gdb) info threads
  2 Thread 0x7f4f6b335700 (LWP 42109)  0x0032214df283 in poll () from 
/lib64/libc.so.6
* 1 Thread 0x7f4f9041c920 (LWP 42108)  0x0032214e1523 in select () from 
/lib64/libc.so.6
(gdb) thread 1
[Switching to thread 1 (Thread 0x7f4f9041c920 (LWP 42108))]#1  
0x007199be in shareinput_reader_waitready (share_id=1, 
planGen=PLANGEN_PLANNER)
at nodeShareInputScan.c:760
760 in nodeShareInputScan.c
(gdb) bt
#0  0x0032214e1523 in select () from /lib64/libc.so.6
#1  0x007199be in shareinput_reader_waitready (share_id=1,