[jira] [Created] (HAWQ-516) gpfdist makefile wrong dependency: install does not depend on make

2016-03-10 Thread Lei Chang (JIRA) 
Lei Chang created HAWQ-516:
--

 Summary: gpfdist makefile wrong dependency: install does not 
depend on make
 Key: HAWQ-516
 URL: https://issues.apache.org/jira/browse/HAWQ-516
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Build
Reporter: Lei Chang
Assignee: Lei Chang


Doing only "make -j8 install" without running "make -j8" first does not install 
"gpfdist".



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

[jira] [Commented] (HAWQ-510) Interconnect error(Could not pare remote listeneraddress '[local]') during running query with generate_series

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-510:
-

GitHub user ictmalili opened a pull request:

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

HAWQ-510. Modify proc->listenerAddr to 127.0.0.1 in entryDB for conne…

Modify proc->listenerAddr to 127.0.0.1 in entryDB for connection to QD

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

$ git pull https://github.com/ictmalili/incubator-hawq HAWQ-510

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

https://github.com/apache/incubator-hawq/pull/436.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 #436


commit 3a18915c410f88f3dfcc1c754d365d7ad1e3dbda
Author: Lili Ma 
Date:   2016-03-11T05:10:03Z

HAWQ-510. Modify proc->listenerAddr to 127.0.0.1 in entryDB for connection 
to QD




> Interconnect error(Could not pare remote listeneraddress '[local]') during 
> running query with generate_series
> -
>
> Key: HAWQ-510
> URL: https://issues.apache.org/jira/browse/HAWQ-510
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Interconnect
>Reporter: Lili Ma
>Assignee: Lili Ma
>
> Running below query meets can't parse remote listeneraddress error.
> {code}
> CREATE TABLE t (key INT, value INT) DISTRIBUTED RANDOMLY;
> INSERT INTO t VALUES (1, 0);
> postgres=# SELECT t2.key, t2.value
> FROM  
> (SELECT key, value 
> FROM t WHERE value = 0) AS t1,
>  (SELECT generate_series(1, 2)::INT AS key, 0::INT AS value ) AS t2   
>  WHERE t1.value = t2.value;
> ERROR:  Interconnect Error: Could not parse remote listeneraddress: '[local]' 
> port '58162': Name or service not known  (seg0 test1:21000 pid=25039)
> DETAIL:  getaddrinfo() unable to parse address: '[local]'
> {code}



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

[jira] [Commented] (HAWQ-515) On Mac 10.10.5, run installcheck-good, there are some warnings around tmpnam

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-515:
-

Github user ictmalili commented on the pull request:

https://github.com/apache/incubator-hawq/pull/435#issuecomment-195192208
  
LGTM. +1


> On Mac 10.10.5, run installcheck-good, there are some warnings around tmpnam
> 
>
> Key: HAWQ-515
> URL: https://issues.apache.org/jira/browse/HAWQ-515
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build, Tests
>Reporter: Lei Chang
>Assignee: Jiali Yao
>
> == running regression test queries==
> test type_sanity  ... Calling POSIX::tmpnam() is deprecated at 
> /Users/changlei/curwork/git/incubator-hawq/inst/bin/gpdiff.pl line 168.
> ok (0.05 sec)
> test querycontext ... Calling POSIX::tmpnam() is deprecated at 
> /Users/changlei/curwork/git/incubator-hawq/inst/bin/gpdiff.pl line 168.
> ok (3.66 sec)



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

[jira] [Commented] (HAWQ-515) On Mac 10.10.5, run installcheck-good, there are some warnings around tmpnam

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-515:
-

GitHub user changleicn opened a pull request:

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

HAWQ-515. Fix warnings around tmpnam when running installcheck-good o…



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

$ git pull https://github.com/changleicn/incubator-hawq HAWQ-515

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

https://github.com/apache/incubator-hawq/pull/435.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 #435


commit 874250d5fc7cce7d266ddb46b697751fda2b82e1
Author: Lei Chang 
Date:   2016-03-11T05:03:05Z

HAWQ-515. Fix warnings around tmpnam when running installcheck-good on MAC




> On Mac 10.10.5, run installcheck-good, there are some warnings around tmpnam
> 
>
> Key: HAWQ-515
> URL: https://issues.apache.org/jira/browse/HAWQ-515
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build, Tests
>Reporter: Lei Chang
>Assignee: Jiali Yao
>
> == running regression test queries==
> test type_sanity  ... Calling POSIX::tmpnam() is deprecated at 
> /Users/changlei/curwork/git/incubator-hawq/inst/bin/gpdiff.pl line 168.
> ok (0.05 sec)
> test querycontext ... Calling POSIX::tmpnam() is deprecated at 
> /Users/changlei/curwork/git/incubator-hawq/inst/bin/gpdiff.pl line 168.
> ok (3.66 sec)



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

[jira] [Created] (HAWQ-515) On Mac 10.10.5, run installcheck-good, there are some warnings around tmpnam

2016-03-10 Thread Lei Chang (JIRA) 
Lei Chang created HAWQ-515:
--

 Summary: On Mac 10.10.5, run installcheck-good, there are some 
warnings around tmpnam
 Key: HAWQ-515
 URL: https://issues.apache.org/jira/browse/HAWQ-515
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Build, Tests
Reporter: Lei Chang
Assignee: Jiali Yao



== running regression test queries==
test type_sanity  ... Calling POSIX::tmpnam() is deprecated at 
/Users/changlei/curwork/git/incubator-hawq/inst/bin/gpdiff.pl line 168.
ok (0.05 sec)
test querycontext ... Calling POSIX::tmpnam() is deprecated at 
/Users/changlei/curwork/git/incubator-hawq/inst/bin/gpdiff.pl line 168.
ok (3.66 sec)




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

[jira] [Commented] (HAWQ-511) Improve HAWQ command line tools running speed and logs

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-511:
-

Github user asfgit closed the pull request at:

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


> Improve HAWQ command line tools running speed and logs
> --
>
> Key: HAWQ-511
> URL: https://issues.apache.org/jira/browse/HAWQ-511
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Command Line Tools
>Reporter: Radar Lei
>Assignee: Lei Chang
>
> Some hawq start/stop/init/activate checks should be doing in parallel, this 
> can reduce many time cost in large cluster.
> BTW, add some checks, enhance some log messages.



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

[jira] [Commented] (HAWQ-511) Improve HAWQ command line tools running speed and logs

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-511:
-

GitHub user radarwave opened a pull request:

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

HAWQ-511. Improve HAWQ command line tools running speed and logs



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

$ git pull https://github.com/radarwave/incubator-hawq HAWQ-511

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

https://github.com/apache/incubator-hawq/pull/434.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 #434


commit 3debd597e86064d10df71162b9fbd2b979da51f4
Author: rlei 
Date:   2016-03-09T14:27:03Z

HAWQ-511. Improve HAWQ command line tools running speed and logs




> Improve HAWQ command line tools running speed and logs
> --
>
> Key: HAWQ-511
> URL: https://issues.apache.org/jira/browse/HAWQ-511
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Command Line Tools
>Reporter: Radar Lei
>Assignee: Lei Chang
>
> Some hawq start/stop/init/activate checks should be doing in parallel, this 
> can reduce many time cost in large cluster.
> BTW, add some checks, enhance some log messages.



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

[jira] [Closed] (HAWQ-480) HAWQ RM does not calculate correct yarn cluster volume

2016-03-10 Thread Yi Jin (JIRA) 

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

Yi Jin closed HAWQ-480.
---

> HAWQ RM does not calculate correct yarn cluster volume
> --
>
> Key: HAWQ-480
> URL: https://issues.apache.org/jira/browse/HAWQ-480
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Yi Jin
>Assignee: Yi Jin
> Fix For: 2.0.0
>
>
> PST,,,p52869,th11406317440,con4,,seg-1,"LOG","0","Removed 
> pending GRM request from root resource queue by (2048 MB, 1.00 CORE) to 
> (0 MB, 0.00 CORE)",,,0,,"resqueuemanager.c",4343,
> 2016-02-29 22:34:17.481384 
> PST,,,p52869,th11406317440,con4,,seg-1,"FATAL","XX000","HAWQ RM 
> Validation. Allocated too much resource in resource pool. (8192 MB, 4.00 
> CORE) (resourcepool.c:3835)",,,0,,"resourcepool.c",3835,"Stack trace:
> 10x87152f postgres  + 0x87152f
> 20x871c09 postgres elog_finish + 0xa9
> 30x8ddd41 postgres validateResourcePoolStatus + 0x501
> 40x8fd517 postgres MainHandlerLoop + 0x1a7
> 50x8fda20 postgres ResManagerMainServer2ndPhase + 0x1e0
> 60x8fde54 postgres ResManagerMain + 0x394
> 70x8fe1e1 postgres ResManagerProcessStartup + 0x181
> 80x75e0c8 postgres  + 0x75e0c8
> 90x75ef82 postgres  + 0x75ef82
> 10   0x76432d postgres  + 0x76432d
> 11   0x765e8e postgres PostmasterMain + 0xc7e
> 12   0x6c029a postgres main + 0x48a
> 13   0x3c1e81ed1d libc.so.6 __libc_start_main + 0xfd
> 14   0x4a1c39 postgres  + 0x4a1c39
> "



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

[jira] [Resolved] (HAWQ-480) HAWQ RM does not calculate correct yarn cluster volume

2016-03-10 Thread Yi Jin (JIRA) 

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

Yi Jin resolved HAWQ-480.
-
   Resolution: Fixed
Fix Version/s: 2.0.0

> HAWQ RM does not calculate correct yarn cluster volume
> --
>
> Key: HAWQ-480
> URL: https://issues.apache.org/jira/browse/HAWQ-480
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Yi Jin
>Assignee: Yi Jin
> Fix For: 2.0.0
>
>
> PST,,,p52869,th11406317440,con4,,seg-1,"LOG","0","Removed 
> pending GRM request from root resource queue by (2048 MB, 1.00 CORE) to 
> (0 MB, 0.00 CORE)",,,0,,"resqueuemanager.c",4343,
> 2016-02-29 22:34:17.481384 
> PST,,,p52869,th11406317440,con4,,seg-1,"FATAL","XX000","HAWQ RM 
> Validation. Allocated too much resource in resource pool. (8192 MB, 4.00 
> CORE) (resourcepool.c:3835)",,,0,,"resourcepool.c",3835,"Stack trace:
> 10x87152f postgres  + 0x87152f
> 20x871c09 postgres elog_finish + 0xa9
> 30x8ddd41 postgres validateResourcePoolStatus + 0x501
> 40x8fd517 postgres MainHandlerLoop + 0x1a7
> 50x8fda20 postgres ResManagerMainServer2ndPhase + 0x1e0
> 60x8fde54 postgres ResManagerMain + 0x394
> 70x8fe1e1 postgres ResManagerProcessStartup + 0x181
> 80x75e0c8 postgres  + 0x75e0c8
> 90x75ef82 postgres  + 0x75ef82
> 10   0x76432d postgres  + 0x76432d
> 11   0x765e8e postgres PostmasterMain + 0xc7e
> 12   0x6c029a postgres main + 0x48a
> 13   0x3c1e81ed1d libc.so.6 __libc_start_main + 0xfd
> 14   0x4a1c39 postgres  + 0x4a1c39
> "



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

[jira] [Commented] (HAWQ-480) HAWQ RM does not calculate correct yarn cluster volume

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-480:
-

Github user jiny2 closed the pull request at:

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


> HAWQ RM does not calculate correct yarn cluster volume
> --
>
> Key: HAWQ-480
> URL: https://issues.apache.org/jira/browse/HAWQ-480
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Yi Jin
>Assignee: Yi Jin
>
> PST,,,p52869,th11406317440,con4,,seg-1,"LOG","0","Removed 
> pending GRM request from root resource queue by (2048 MB, 1.00 CORE) to 
> (0 MB, 0.00 CORE)",,,0,,"resqueuemanager.c",4343,
> 2016-02-29 22:34:17.481384 
> PST,,,p52869,th11406317440,con4,,seg-1,"FATAL","XX000","HAWQ RM 
> Validation. Allocated too much resource in resource pool. (8192 MB, 4.00 
> CORE) (resourcepool.c:3835)",,,0,,"resourcepool.c",3835,"Stack trace:
> 10x87152f postgres  + 0x87152f
> 20x871c09 postgres elog_finish + 0xa9
> 30x8ddd41 postgres validateResourcePoolStatus + 0x501
> 40x8fd517 postgres MainHandlerLoop + 0x1a7
> 50x8fda20 postgres ResManagerMainServer2ndPhase + 0x1e0
> 60x8fde54 postgres ResManagerMain + 0x394
> 70x8fe1e1 postgres ResManagerProcessStartup + 0x181
> 80x75e0c8 postgres  + 0x75e0c8
> 90x75ef82 postgres  + 0x75ef82
> 10   0x76432d postgres  + 0x76432d
> 11   0x765e8e postgres PostmasterMain + 0xc7e
> 12   0x6c029a postgres main + 0x48a
> 13   0x3c1e81ed1d libc.so.6 __libc_start_main + 0xfd
> 14   0x4a1c39 postgres  + 0x4a1c39
> "



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

[jira] [Commented] (HAWQ-480) HAWQ RM does not calculate correct yarn cluster volume

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-480:
-

Github user linwen commented on the pull request:

https://github.com/apache/incubator-hawq/pull/432#issuecomment-195146263
  
+1


> HAWQ RM does not calculate correct yarn cluster volume
> --
>
> Key: HAWQ-480
> URL: https://issues.apache.org/jira/browse/HAWQ-480
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Yi Jin
>Assignee: Yi Jin
>
> PST,,,p52869,th11406317440,con4,,seg-1,"LOG","0","Removed 
> pending GRM request from root resource queue by (2048 MB, 1.00 CORE) to 
> (0 MB, 0.00 CORE)",,,0,,"resqueuemanager.c",4343,
> 2016-02-29 22:34:17.481384 
> PST,,,p52869,th11406317440,con4,,seg-1,"FATAL","XX000","HAWQ RM 
> Validation. Allocated too much resource in resource pool. (8192 MB, 4.00 
> CORE) (resourcepool.c:3835)",,,0,,"resourcepool.c",3835,"Stack trace:
> 10x87152f postgres  + 0x87152f
> 20x871c09 postgres elog_finish + 0xa9
> 30x8ddd41 postgres validateResourcePoolStatus + 0x501
> 40x8fd517 postgres MainHandlerLoop + 0x1a7
> 50x8fda20 postgres ResManagerMainServer2ndPhase + 0x1e0
> 60x8fde54 postgres ResManagerMain + 0x394
> 70x8fe1e1 postgres ResManagerProcessStartup + 0x181
> 80x75e0c8 postgres  + 0x75e0c8
> 90x75ef82 postgres  + 0x75ef82
> 10   0x76432d postgres  + 0x76432d
> 11   0x765e8e postgres PostmasterMain + 0xc7e
> 12   0x6c029a postgres main + 0x48a
> 13   0x3c1e81ed1d libc.so.6 __libc_start_main + 0xfd
> 14   0x4a1c39 postgres  + 0x4a1c39
> "



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

[jira] [Commented] (HAWQ-499) IPv6 address not read properly on OSX version < 10.11

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-499:
-

Github user jfrank-pivotal commented on the pull request:

https://github.com/apache/incubator-hawq/pull/419#issuecomment-195146039
  
We don't run any of those OS versions here, but we can try to test it with 
Vagrant.  Alternatively, we can add the `ip` executable to the list of 
toolchain requirements (but I'd prefer the former).  @radarwave, what OSX 
version should we target for testing?


> IPv6 address not read properly on OSX version < 10.11
> -
>
> Key: HAWQ-499
> URL: https://issues.apache.org/jira/browse/HAWQ-499
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Jacob Max Frank
>Assignee: Lei Chang
>
> The commit 91c50f70 for HAWQ-235 fixed IP lookup for IPv4, but appears to 
> have missed the corresponding case for IPv6.
> On my laptop (currently running OSX 10.10.15), I hit the else case in this 
> block from *hawqinit.sh*:
> {code}
> get_master_ipv6_addresses() {
> if [ "${distro_based_on}" = "Mac" ] && [ "${distro_version:0:5}" = 
> "10.11" ]; then
> MASTER_IPV6_LOCAL_ADDRESS_ALL=(`${IFCONFIG} | ${GREP} inet6 | ${AWK} 
> '{print $2}' | cut -d'%' -f1`)
> else
> MASTER_IPV6_LOCAL_ADDRESS_ALL=(`ip -6 address show |${GREP} 
> inet6|${AWK} '{print $2}' |cut -d'/' -f1`)
> fi
> }
> {code}
> That resulted in this error, since the "ip" command isn't on my computer:
> {code}
> /usr/local/hawq/bin/lib/hawqinit.sh: line 196: ip: command not found
> {code}
> We verified that the positive case in the block above works fine on my 
> version of OSX.  I can't say for sure how it will work on older OSX versions, 
> but IPv6 has been supported since OSX 10.1.
> We're open to suggestions for the bug's most relevant "component"; "build" 
> was the closest but didn't really seem to fit.  Perhaps we could add a 
> component for support/infrastructure scripts.



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

[jira] [Commented] (HAWQ-480) HAWQ RM does not calculate correct yarn cluster volume

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-480:
-

Github user yaoj2 commented on the pull request:

https://github.com/apache/incubator-hawq/pull/432#issuecomment-195144591
  
+1


> HAWQ RM does not calculate correct yarn cluster volume
> --
>
> Key: HAWQ-480
> URL: https://issues.apache.org/jira/browse/HAWQ-480
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Yi Jin
>Assignee: Yi Jin
>
> PST,,,p52869,th11406317440,con4,,seg-1,"LOG","0","Removed 
> pending GRM request from root resource queue by (2048 MB, 1.00 CORE) to 
> (0 MB, 0.00 CORE)",,,0,,"resqueuemanager.c",4343,
> 2016-02-29 22:34:17.481384 
> PST,,,p52869,th11406317440,con4,,seg-1,"FATAL","XX000","HAWQ RM 
> Validation. Allocated too much resource in resource pool. (8192 MB, 4.00 
> CORE) (resourcepool.c:3835)",,,0,,"resourcepool.c",3835,"Stack trace:
> 10x87152f postgres  + 0x87152f
> 20x871c09 postgres elog_finish + 0xa9
> 30x8ddd41 postgres validateResourcePoolStatus + 0x501
> 40x8fd517 postgres MainHandlerLoop + 0x1a7
> 50x8fda20 postgres ResManagerMainServer2ndPhase + 0x1e0
> 60x8fde54 postgres ResManagerMain + 0x394
> 70x8fe1e1 postgres ResManagerProcessStartup + 0x181
> 80x75e0c8 postgres  + 0x75e0c8
> 90x75ef82 postgres  + 0x75ef82
> 10   0x76432d postgres  + 0x76432d
> 11   0x765e8e postgres PostmasterMain + 0xc7e
> 12   0x6c029a postgres main + 0x48a
> 13   0x3c1e81ed1d libc.so.6 __libc_start_main + 0xfd
> 14   0x4a1c39 postgres  + 0x4a1c39
> "



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

[jira] [Resolved] (HAWQ-512) Query hang due to deadlock in entrydb catalog access

2016-03-10 Thread zhenglin tao (JIRA) 

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

zhenglin tao resolved HAWQ-512.
---
Resolution: Fixed

> Query hang due to deadlock in entrydb catalog access
> 
>
> Key: HAWQ-512
> URL: https://issues.apache.org/jira/browse/HAWQ-512
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Catalog
>Affects Versions: 2.0.0-beta-incubating
>Reporter: zhenglin tao
>Assignee: zhenglin tao
> Fix For: 2.0.0
>
>
> When entry database is involved in query with joins, it may hang due to 
> deadlock while accessing catalog.
> {noformat}
> DROP TABLE IF EXISTS t;
> CREATE TABLE t (key INT, value INT) DISTRIBUTED RANDOMLY;
> INSERT INTO t VALUES (1, 0);
> CREATE OR REPLACE FUNCTION f()
> RETURNS VOID AS $$
> sql = """ALTER TABLE t SET DISTRIBUTED BY (key)"""
> plpy.execute(sql)
> sql = """INSERT INTO t
>  SELECT t2.key, t2.value
>  FROM
>  (SELECT key, value FROM t WHERE value = 0) AS t1,
>  (SELECT generate_series(1, 2)::INT AS key, 0::INT AS value ) 
> AS t2
>  WHERE t1.value = t2.value """
> # plan = plpy.prepare(sql)
> plpy.execute(sql)
> $$
> LANGUAGE plpythonu VOLATILE;
> -- Call of function f() hangs here
> SELECT f();
> {noformat}



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

[jira] [Updated] (HAWQ-514) Update and add to PXF Rpm 'Summary' and 'Description' metadata

2016-03-10 Thread Goden Yao (JIRA) 

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

Goden Yao updated HAWQ-514:
---
Fix Version/s: 2.0.0

> Update and add to PXF Rpm 'Summary' and 'Description' metadata
> --
>
> Key: HAWQ-514
> URL: https://issues.apache.org/jira/browse/HAWQ-514
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: PXF
>Reporter: Kavinder Dhaliwal
>Assignee: Kavinder Dhaliwal
> Fix For: 2.0.0
>
>
> Currently the build.gradle script in "pxf" outputs the following information 
> for all pxf rpms:
> {code}
> Summary : The PXF extensions library for HAWQ
> Description :
> {code}
> The summary should read "HAWQ extension framework" and the description should 
> include relevant information about the rpm.



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

[jira] [Updated] (HAWQ-514) Update and add to PXF Rpm 'Summary' and 'Description' metadata

2016-03-10 Thread Goden Yao (JIRA) 

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

Goden Yao updated HAWQ-514:
---
Component/s: PXF

> Update and add to PXF Rpm 'Summary' and 'Description' metadata
> --
>
> Key: HAWQ-514
> URL: https://issues.apache.org/jira/browse/HAWQ-514
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: PXF
>Reporter: Kavinder Dhaliwal
>Assignee: Kavinder Dhaliwal
> Fix For: 2.0.0
>
>
> Currently the build.gradle script in "pxf" outputs the following information 
> for all pxf rpms:
> {code}
> Summary : The PXF extensions library for HAWQ
> Description :
> {code}
> The summary should read "HAWQ extension framework" and the description should 
> include relevant information about the rpm.



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

[jira] [Commented] (HAWQ-502) Support --enable-orca in autoconf

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-502:
-

Github user hsyuan commented on the pull request:

https://github.com/apache/incubator-hawq/pull/420#issuecomment-195113382
  
+1


> Support --enable-orca in autoconf
> -
>
> Key: HAWQ-502
> URL: https://issues.apache.org/jira/browse/HAWQ-502
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Optimizer
>Reporter: Jacob Max Frank
>Assignee: Amr El-Helw
>
> Autoconf and Makefile changes are needed to build with HAWQ with GPORCA.  We 
> spent some time hacking on this and will file a PR soon.



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

[jira] [Assigned] (HAWQ-514) Update and add to PXF Rpm 'Summary' and 'Description' metadata

2016-03-10 Thread Kavinder Dhaliwal (JIRA) 

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

Kavinder Dhaliwal reassigned HAWQ-514:
--

Assignee: Kavinder Dhaliwal  (was: Lei Chang)

> Update and add to PXF Rpm 'Summary' and 'Description' metadata
> --
>
> Key: HAWQ-514
> URL: https://issues.apache.org/jira/browse/HAWQ-514
> Project: Apache HAWQ
>  Issue Type: Improvement
>Reporter: Kavinder Dhaliwal
>Assignee: Kavinder Dhaliwal
>
> Currently the build.gradle script in "pxf" outputs the following information 
> for all pxf rpms:
> {code}
> Summary : The PXF extensions library for HAWQ
> Description :
> {code}
> The summary should read "HAWQ extension framework" and the description should 
> include relevant information about the rpm.



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

[jira] [Commented] (HAWQ-452) Remove workfile views from hawq_toolkit

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-452:
-

Github user hsyuan commented on the pull request:

https://github.com/apache/incubator-hawq/pull/385#issuecomment-195075969
  
LGTM.


> Remove workfile views from hawq_toolkit
> ---
>
> Key: HAWQ-452
> URL: https://issues.apache.org/jira/browse/HAWQ-452
> Project: Apache HAWQ
>  Issue Type: Task
>  Components: Query Execution
>Reporter: George Caragea
>Assignee: George Caragea
>
> In the hawq_toolkit schema we have a few views with live information about 
> disk space used for workfiles (or spillfiles). 
> Generating this views means running a UDF on every segment. This doesn't 
> apply to the HAWQ 2 architecture: 
> *  The notion of "every segment" is not well defined in HAWQ 2, since we have 
> virtual segments that are created dynamically based on resource requirements 
> and availablitiy
> * There is no mechanism to execute a UDF on all the existing virtual or 
> physical segments 
> We should remove the views from hawq_toolkit.



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

[jira] [Commented] (HAWQ-499) IPv6 address not read properly on OSX version < 10.11

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-499:
-

Github user hsyuan commented on the pull request:

https://github.com/apache/incubator-hawq/pull/419#issuecomment-195075440
  
LGTM.


> IPv6 address not read properly on OSX version < 10.11
> -
>
> Key: HAWQ-499
> URL: https://issues.apache.org/jira/browse/HAWQ-499
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Jacob Max Frank
>Assignee: Lei Chang
>
> The commit 91c50f70 for HAWQ-235 fixed IP lookup for IPv4, but appears to 
> have missed the corresponding case for IPv6.
> On my laptop (currently running OSX 10.10.15), I hit the else case in this 
> block from *hawqinit.sh*:
> {code}
> get_master_ipv6_addresses() {
> if [ "${distro_based_on}" = "Mac" ] && [ "${distro_version:0:5}" = 
> "10.11" ]; then
> MASTER_IPV6_LOCAL_ADDRESS_ALL=(`${IFCONFIG} | ${GREP} inet6 | ${AWK} 
> '{print $2}' | cut -d'%' -f1`)
> else
> MASTER_IPV6_LOCAL_ADDRESS_ALL=(`ip -6 address show |${GREP} 
> inet6|${AWK} '{print $2}' |cut -d'/' -f1`)
> fi
> }
> {code}
> That resulted in this error, since the "ip" command isn't on my computer:
> {code}
> /usr/local/hawq/bin/lib/hawqinit.sh: line 196: ip: command not found
> {code}
> We verified that the positive case in the block above works fine on my 
> version of OSX.  I can't say for sure how it will work on older OSX versions, 
> but IPv6 has been supported since OSX 10.1.
> We're open to suggestions for the bug's most relevant "component"; "build" 
> was the closest but didn't really seem to fit.  Perhaps we could add a 
> component for support/infrastructure scripts.



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

[jira] [Created] (HAWQ-513) initdb.c failed on OSX 10.11.3 due to fgets error

2016-03-10 Thread xin zhang (JIRA) 
xin zhang created HAWQ-513:
--

 Summary: initdb.c failed on OSX 10.11.3 due to fgets error
 Key: HAWQ-513
 URL: https://issues.apache.org/jira/browse/HAWQ-513
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Unknown
Reporter: xin zhang
Assignee: Lei Chang


we hit following strange issue on OSX 10.11.3:

The error message in the initdb is: 
{code}
20160301:00:00:26:075823 hawq_init:This-MacBook-Pro:vagrant-[INFO]:-Start to 
init master node: 'localhost'
sh: line 1: 76106 Trace/BPT trap: 5   "/usr/local/hawq/bin/postgres" -V 2> 
/dev/null
fgets failure: Undefined error: 0
The program "postgres" is needed by initdb but was either not found in the same 
directory as "/usr/local/hawq/bin/initdb" or failed unexpectedly.
Check your installation; "postgres -V" may have more information.
Master postgres initdb failed
{code}

We suspect the issue due to the newer version of the libSystem.B.dylib on OSX 
10.11.3.

Here is the details of the dependencies of `postgres` and `initdb`:

10.10.5, postgres can start, and initdb succeed:
{code}
[bin: xzhang{master}]$ otool -L postgres
postgres:
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 
120.0.0)
libhdfs3.1.dylib (compatibility version 1.0.0, current version 2.2.30)
/usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version 
10.9.0)
libyarn.1.dylib (compatibility version 1.0.0, current version 0.1.13)
/usr/local/opt/json-c/lib/libjson-c.2.dylib (compatibility version 3.0.0, 
current version 3.1.0)
/usr/local/opt/snappy/lib/libsnappy.1.dylib (compatibility version 5.0.0, 
current version 5.0.0)
/usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 
1.0.5)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1213.0.0)
/usr/lib/libcurl.4.dylib (compatibility version 7.0.0, current version 
8.0.0)
/System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 
(compatibility version 5.0.0, current version 6.0.0)
libdxltranslators.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/local/opt/thrift/lib/libthrift-0.9.3.dylib (compatibility version 
0.0.0, current version 0.0.0)

This-MacBook-Pro:bin vagrant$ otool -L initdb
initdb:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1226.10.1)
{code}

10.11.3, postgres can start, but initdb failed:

{code}
This-MacBook-Pro:bin vagrant$ otool -L postgres
postgres:
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 
120.1.0)
libhdfs3.1.dylib (compatibility version 1.0.0, current version 2.2.30)
/usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version 
10.9.0)
libyarn.1.dylib (compatibility version 1.0.0, current version 0.1.13)
/usr/local/opt/json-c/lib/libjson-c.2.dylib (compatibility version 3.0.0, 
current version 3.1.0)
/usr/local/opt/snappy/lib/libsnappy.1.dylib (compatibility version 5.0.0, 
current version 5.0.0)
/usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 
1.0.5)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 
0.9.8)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current 
version 0.9.8)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1226.10.1)
/usr/lib/libcurl.4.dylib (compatibility version 7.0.0, current version 
8.0.0)
/System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 
(compatibility version 5.0.0, current version 6.0.0)
libdxltranslators.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/local/opt/thrift/lib/libthrift-0.9.3.dylib (compatibility version 
0.0.0, current version 0.0.0)

[bin: xzhang{master}]$ otool -L initdb
initdb:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
1213.0.0)
{code}

In this case, there is a difference between the two OS regarding to the 
libSystem.B.dylib.

Question is how to fix it? For example, how to change the libSystem.B.dylib to 
an older version? or, how to fix the postgres or initdb so that they works on 
the new OSX 10.11.3?



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

[jira] [Updated] (HAWQ-501) Switch from using hcatalog as the reserve keyword

2016-03-10 Thread Goden Yao (JIRA) 

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

Goden Yao updated HAWQ-501:
---
Fix Version/s: backlog

> Switch from using hcatalog as the reserve keyword
> -
>
> Key: HAWQ-501
> URL: https://issues.apache.org/jira/browse/HAWQ-501
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: External Tables, Hcatalog, PXF
>Reporter: Shivram Mani
>Assignee: Goden Yao
>Priority: Minor
> Fix For: backlog
>
>
> An alternative means of accessing hive tables is for the user to use hcatalog 
> as the keyword eg: table default.customers will be accessed as 
> hcatalog.default.customers.
> The end user must not be aware of the underlying catalog store and should 
> instead only be aware of hive/hbase/hdfs.
> The above table can instead be accessed via hive.default.customers.
> This allows us to expand this approach to also work with other datasources 
> once schema auto discovery is complete HAWQ-450 and HAWQ-500
> A file on HBase can be accessed using hbase. 



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

[jira] [Commented] (HAWQ-480) HAWQ RM does not calculate correct yarn cluster volume

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-480:
-

GitHub user jiny2 opened a pull request:

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

HAWQ-480. HAWQ RM does not calculate correct yarn cluster volume



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

$ git pull https://github.com/jiny2/incubator-hawq HAWQ-480-2

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

https://github.com/apache/incubator-hawq/pull/432.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 #432


commit 9f4cb225d517f392aa95e517c80b44a0a915ac4e
Author: YI JIN 
Date:   2016-03-10T10:52:57Z

HAWQ-480. HAWQ RM does not calculate correct yarn cluster volume




> HAWQ RM does not calculate correct yarn cluster volume
> --
>
> Key: HAWQ-480
> URL: https://issues.apache.org/jira/browse/HAWQ-480
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Yi Jin
>Assignee: Yi Jin
>
> PST,,,p52869,th11406317440,con4,,seg-1,"LOG","0","Removed 
> pending GRM request from root resource queue by (2048 MB, 1.00 CORE) to 
> (0 MB, 0.00 CORE)",,,0,,"resqueuemanager.c",4343,
> 2016-02-29 22:34:17.481384 
> PST,,,p52869,th11406317440,con4,,seg-1,"FATAL","XX000","HAWQ RM 
> Validation. Allocated too much resource in resource pool. (8192 MB, 4.00 
> CORE) (resourcepool.c:3835)",,,0,,"resourcepool.c",3835,"Stack trace:
> 10x87152f postgres  + 0x87152f
> 20x871c09 postgres elog_finish + 0xa9
> 30x8ddd41 postgres validateResourcePoolStatus + 0x501
> 40x8fd517 postgres MainHandlerLoop + 0x1a7
> 50x8fda20 postgres ResManagerMainServer2ndPhase + 0x1e0
> 60x8fde54 postgres ResManagerMain + 0x394
> 70x8fe1e1 postgres ResManagerProcessStartup + 0x181
> 80x75e0c8 postgres  + 0x75e0c8
> 90x75ef82 postgres  + 0x75ef82
> 10   0x76432d postgres  + 0x76432d
> 11   0x765e8e postgres PostmasterMain + 0xc7e
> 12   0x6c029a postgres main + 0x48a
> 13   0x3c1e81ed1d libc.so.6 __libc_start_main + 0xfd
> 14   0x4a1c39 postgres  + 0x4a1c39
> "



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

[jira] [Commented] (HAWQ-512) Query hang due to deadlock in entrydb catalog access

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-512:
-

Github user asfgit closed the pull request at:

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


> Query hang due to deadlock in entrydb catalog access
> 
>
> Key: HAWQ-512
> URL: https://issues.apache.org/jira/browse/HAWQ-512
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Catalog
>Affects Versions: 2.0.0-beta-incubating
>Reporter: zhenglin tao
>Assignee: zhenglin tao
> Fix For: 2.0.0
>
>
> When entry database is involved in query with joins, it may hang due to 
> deadlock while accessing catalog.
> {noformat}
> DROP TABLE IF EXISTS t;
> CREATE TABLE t (key INT, value INT) DISTRIBUTED RANDOMLY;
> INSERT INTO t VALUES (1, 0);
> CREATE OR REPLACE FUNCTION f()
> RETURNS VOID AS $$
> sql = """ALTER TABLE t SET DISTRIBUTED BY (key)"""
> plpy.execute(sql)
> sql = """INSERT INTO t
>  SELECT t2.key, t2.value
>  FROM
>  (SELECT key, value FROM t WHERE value = 0) AS t1,
>  (SELECT generate_series(1, 2)::INT AS key, 0::INT AS value ) 
> AS t2
>  WHERE t1.value = t2.value """
> # plan = plpy.prepare(sql)
> plpy.execute(sql)
> $$
> LANGUAGE plpythonu VOLATILE;
> -- Call of function f() hangs here
> SELECT f();
> {noformat}



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

[jira] [Commented] (HAWQ-512) Query hang due to deadlock in entrydb catalog access

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-512:
-

Github user huor commented on the pull request:

https://github.com/apache/incubator-hawq/pull/431#issuecomment-194778876
  
LGTM. +1


> Query hang due to deadlock in entrydb catalog access
> 
>
> Key: HAWQ-512
> URL: https://issues.apache.org/jira/browse/HAWQ-512
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Catalog
>Affects Versions: 2.0.0-beta-incubating
>Reporter: zhenglin tao
>Assignee: zhenglin tao
> Fix For: 2.0.0
>
>
> When entry database is involved in query with joins, it may hang due to 
> deadlock while accessing catalog.
> {noformat}
> DROP TABLE IF EXISTS t;
> CREATE TABLE t (key INT, value INT) DISTRIBUTED RANDOMLY;
> INSERT INTO t VALUES (1, 0);
> CREATE OR REPLACE FUNCTION f()
> RETURNS VOID AS $$
> sql = """ALTER TABLE t SET DISTRIBUTED BY (key)"""
> plpy.execute(sql)
> sql = """INSERT INTO t
>  SELECT t2.key, t2.value
>  FROM
>  (SELECT key, value FROM t WHERE value = 0) AS t1,
>  (SELECT generate_series(1, 2)::INT AS key, 0::INT AS value ) 
> AS t2
>  WHERE t1.value = t2.value """
> # plan = plpy.prepare(sql)
> plpy.execute(sql)
> $$
> LANGUAGE plpythonu VOLATILE;
> -- Call of function f() hangs here
> SELECT f();
> {noformat}



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

[jira] [Updated] (HAWQ-512) Query hang due to deadlock in entrydb catalog access

2016-03-10 Thread Ruilong Huo (JIRA) 

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

Ruilong Huo updated HAWQ-512:
-
Component/s: Catalog

> Query hang due to deadlock in entrydb catalog access
> 
>
> Key: HAWQ-512
> URL: https://issues.apache.org/jira/browse/HAWQ-512
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Catalog
>Affects Versions: 2.0.0-beta-incubating
>Reporter: zhenglin tao
>Assignee: Lei Chang
> Fix For: 2.0.0
>
>
> When entry database is involved in query with joins, it may hang due to 
> deadlock while accessing catalog.
> {noformat}
> DROP TABLE IF EXISTS t;
> CREATE TABLE t (key INT, value INT) DISTRIBUTED RANDOMLY;
> INSERT INTO t VALUES (1, 0);
> CREATE OR REPLACE FUNCTION f()
> RETURNS VOID AS $$
> sql = """ALTER TABLE t SET DISTRIBUTED BY (key)"""
> plpy.execute(sql)
> sql = """INSERT INTO t
>  SELECT t2.key, t2.value
>  FROM
>  (SELECT key, value FROM t WHERE value = 0) AS t1,
>  (SELECT generate_series(1, 2)::INT AS key, 0::INT AS value ) 
> AS t2
>  WHERE t1.value = t2.value """
> # plan = plpy.prepare(sql)
> plpy.execute(sql)
> $$
> LANGUAGE plpythonu VOLATILE;
> -- Call of function f() hangs here
> SELECT f();
> {noformat}



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

[jira] [Commented] (HAWQ-512) Query hang due to deadlock in entrydb catalog access

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-512:
-

GitHub user ztao1987 opened a pull request:

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

HAWQ-512. Fix query hang due to deadlock in entrydb catalog access



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

$ git pull https://github.com/ztao1987/incubator-hawq HAWQ-512

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

https://github.com/apache/incubator-hawq/pull/431.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 #431


commit 88bf600a093d11fcc7c50c8dd934dd1a96f88cd7
Author: zhenglin tao 
Date:   2016-03-10T10:20:16Z

HAWQ-512. Fix query hang due to deadlock in entrydb catalog access




> Query hang due to deadlock in entrydb catalog access
> 
>
> Key: HAWQ-512
> URL: https://issues.apache.org/jira/browse/HAWQ-512
> Project: Apache HAWQ
>  Issue Type: Bug
>Affects Versions: 2.0.0-beta-incubating
>Reporter: zhenglin tao
>Assignee: Lei Chang
>




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

[jira] [Updated] (HAWQ-512) Query hang due to deadlock in entrydb catalog access

2016-03-10 Thread Ruilong Huo (JIRA) 

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

Ruilong Huo updated HAWQ-512:
-
Affects Version/s: 2.0.0-beta-incubating

> Query hang due to deadlock in entrydb catalog access
> 
>
> Key: HAWQ-512
> URL: https://issues.apache.org/jira/browse/HAWQ-512
> Project: Apache HAWQ
>  Issue Type: Bug
>Affects Versions: 2.0.0-beta-incubating
>Reporter: zhenglin tao
>Assignee: Lei Chang
>
> When entry database is involved in query with joins, it may hang due to 
> deadlock while accessing catalog.
> {noformat}
> DROP TABLE IF EXISTS t;
> CREATE TABLE t (key INT, value INT) DISTRIBUTED RANDOMLY;
> INSERT INTO t VALUES (1, 0);
> CREATE OR REPLACE FUNCTION f()
> RETURNS VOID AS $$
> sql = """ALTER TABLE t SET DISTRIBUTED BY (key)"""
> plpy.execute(sql)
> sql = """INSERT INTO t
>  SELECT t2.key, t2.value
>  FROM
>  (SELECT key, value FROM t WHERE value = 0) AS t1,
>  (SELECT generate_series(1, 2)::INT AS key, 0::INT AS value ) 
> AS t2
>  WHERE t1.value = t2.value """
> # plan = plpy.prepare(sql)
> plpy.execute(sql)
> $$
> LANGUAGE plpythonu VOLATILE;
> -- Call of function f() hangs here
> SELECT f();
> {noformat}



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

[jira] [Updated] (HAWQ-512) Query hang due to deadlock in entrydb catalog access

2016-03-10 Thread Ruilong Huo (JIRA) 

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

Ruilong Huo updated HAWQ-512:
-
Description: 
When entry database is involved in query with joins, it may hang due to 
deadlock while accessing catalog.
{noformat}
DROP TABLE IF EXISTS t;
CREATE TABLE t (key INT, value INT) DISTRIBUTED RANDOMLY;
INSERT INTO t VALUES (1, 0);

CREATE OR REPLACE FUNCTION f()
RETURNS VOID AS $$
sql = """ALTER TABLE t SET DISTRIBUTED BY (key)"""
plpy.execute(sql)

sql = """INSERT INTO t
 SELECT t2.key, t2.value
 FROM
 (SELECT key, value FROM t WHERE value = 0) AS t1,
 (SELECT generate_series(1, 2)::INT AS key, 0::INT AS value ) 
AS t2
 WHERE t1.value = t2.value """
# plan = plpy.prepare(sql)
plpy.execute(sql)
$$
LANGUAGE plpythonu VOLATILE;

-- Call of function f() hangs here
SELECT f();
{noformat}

> Query hang due to deadlock in entrydb catalog access
> 
>
> Key: HAWQ-512
> URL: https://issues.apache.org/jira/browse/HAWQ-512
> Project: Apache HAWQ
>  Issue Type: Bug
>Affects Versions: 2.0.0-beta-incubating
>Reporter: zhenglin tao
>Assignee: Lei Chang
>
> When entry database is involved in query with joins, it may hang due to 
> deadlock while accessing catalog.
> {noformat}
> DROP TABLE IF EXISTS t;
> CREATE TABLE t (key INT, value INT) DISTRIBUTED RANDOMLY;
> INSERT INTO t VALUES (1, 0);
> CREATE OR REPLACE FUNCTION f()
> RETURNS VOID AS $$
> sql = """ALTER TABLE t SET DISTRIBUTED BY (key)"""
> plpy.execute(sql)
> sql = """INSERT INTO t
>  SELECT t2.key, t2.value
>  FROM
>  (SELECT key, value FROM t WHERE value = 0) AS t1,
>  (SELECT generate_series(1, 2)::INT AS key, 0::INT AS value ) 
> AS t2
>  WHERE t1.value = t2.value """
> # plan = plpy.prepare(sql)
> plpy.execute(sql)
> $$
> LANGUAGE plpythonu VOLATILE;
> -- Call of function f() hangs here
> SELECT f();
> {noformat}



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

[jira] [Created] (HAWQ-512) Query hang due to deadlock in entrydb catalog access

2016-03-10 Thread zhenglin tao (JIRA) 
zhenglin tao created HAWQ-512:
-

 Summary: Query hang due to deadlock in entrydb catalog access
 Key: HAWQ-512
 URL: https://issues.apache.org/jira/browse/HAWQ-512
 Project: Apache HAWQ
  Issue Type: Bug
Reporter: zhenglin tao
Assignee: Lei Chang






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

[jira] [Commented] (HAWQ-510) Interconnect error(Could not pare remote listeneraddress '[local]') during running query with generate_series

2016-03-10 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on HAWQ-510:
-

Github user ictmalili closed the pull request at:

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


> Interconnect error(Could not pare remote listeneraddress '[local]') during 
> running query with generate_series
> -
>
> Key: HAWQ-510
> URL: https://issues.apache.org/jira/browse/HAWQ-510
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Interconnect
>Reporter: Lili Ma
>Assignee: Lili Ma
>
> Running below query meets can't parse remote listeneraddress error.
> {code}
> CREATE TABLE t (key INT, value INT) DISTRIBUTED RANDOMLY;
> INSERT INTO t VALUES (1, 0);
> postgres=# SELECT t2.key, t2.value
> FROM  
> (SELECT key, value 
> FROM t WHERE value = 0) AS t1,
>  (SELECT generate_series(1, 2)::INT AS key, 0::INT AS value ) AS t2   
>  WHERE t1.value = t2.value;
> ERROR:  Interconnect Error: Could not parse remote listeneraddress: '[local]' 
> port '58162': Name or service not known  (seg0 test1:21000 pid=25039)
> DETAIL:  getaddrinfo() unable to parse address: '[local]'
> {code}



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