[GitHub] incubator-hawq pull request: HAWQ-394. Remove pgcrypto from code b...

[paul-guo-]

GitHub user paul-guo- opened a pull request:

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

HAWQ-394. Remove pgcrypto from code base

Removed pycrypto and modified pom.xml.

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

$ git pull https://github.com/paul-guo-/incubator-hawq del-pgcrypto

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

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


commit 7b1cfbd7d54788dac5cd006efa1bf69072e5e33d
Author: Paul Guo 
Date:   2016-05-13T02:55:48Z

HAWQ-394. Remove pgcrypto from code base




---
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.
---

Re: HAWQ YARN RPC Errors

[Wen Lin]

Hi, Gagan,

It seems a sync failure between QD and Resource Manager. Not related to
libyarn 's RPC.
Would you like to attach the master's log file? Thanks!

On Fri, May 13, 2016 at 12:58 AM, Gagan Brahmi 
wrote:

> Hi Team,
>
> Do we have some recommended tuning for the RPC warning/errors
> encountered intermittently?
>
> The error which is seen is the following:
>
> WARNING:  Sync RPC framework (inet) finds exception raised.
> ERROR:  failed to return resource to resource manager, failed to
> receive content (pquery.c:991)
>
> This error however, disappears when we retry the query. There are
> cases when the query is to be retried more than once.
>
> The error looks to be invoked when COMM2RM_CLIENT_FAIL_RECV is encountered.
>
> The setup is using YARN resource manager. And the following is the
> yarn-client configuration used:
>
> 
>
> 
>   hadoop.security.authentication
>   kerberos
> 
>
> 
>   rpc.client.connect.retry
>   10
> 
>
> 
>   rpc.client.connect.tcpnodelay
>   true
> 
>
> 
>   rpc.client.connect.timeout
>   60
> 
>
> 
>   rpc.client.max.idle
>   1
> 
>
> 
>   rpc.client.ping.interval
>   1
> 
>
> 
>   rpc.client.read.timeout
>   360
> 
>
> 
>   rpc.client.socket.linger.timeout
>   -1
> 
>
> 
>   rpc.client.timeout
>   360
> 
>
> 
>   rpc.client.write.timeout
>   360
> 
>
> 
>   yarn.client.failover.max.attempts
>   15
> 
>
>   
>
> I would appreciate some recommendations.
>
>
> Regards,
> Gagan Brahmi
>

[GitHub] incubator-hawq pull request: Explicitly initialize GPOPT and its d...

[hardikar]

GitHub user hardikar opened a pull request:

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

Explicitly initialize GPOPT and its dependencies.

These were initialized by constructors earlier. To pass any parameters
for initializing GPOPT or any of its dependendencies, we need to do that
explicitly.

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

$ git pull https://github.com/hardikar/incubator-hawq master

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

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


commit 2c8a8c2b16f5ac7a96e5d774d6d7fce0b8e55a39
Author: Shreedhar Hardikar 
Date:   2016-05-13T01:21:29Z

Explicitly initialize GPOPT and its dependencies.

These were initialized by constructors earlier. To pass any parameters
for initializing GPOPT or any of its dependendencies, we need to do that
explicitly.




---
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: HAWQ-732. Workable test framework.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: HAWQ-732. Workable test framework.

[wengyanqing]

Github user wengyanqing commented on the pull request:

https://github.com/apache/incubator-hawq/pull/653#issuecomment-218917503
  
+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.
---

[GitHub] incubator-hawq pull request: HAWQ-732. Workable test framework.

[ztao1987]

GitHub user ztao1987 opened a pull request:

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

HAWQ-732. Workable test framework.



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

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

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

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


commit e066b8b77ea48332108aa292ce32cb5250afc5c5
Author: ztao1987 
Date:   2016-05-12T23:34:51Z

HAWQ-732. Workable test framework.




---
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: HAWQ-713 Make lc_numeric guc to have ...

[karthijrk]

GitHub user karthijrk opened a pull request:

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

HAWQ-713 Make lc_numeric guc to have GUC_GPDB_ADDOPT

Without GUC_GPDB_ADOPT, the values for guc 'lc_numeric' is not dispatched
to the QE processes.

This fix is ported from GPDB.

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

$ git pull https://github.com/karthijrk/incubator-hawq HAWQ-713-lc-numeric

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

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


commit bebce2ac6e4deeadc7ca17c5f783fd85b57c8844
Author: Karthikeyan Jambu Rajaraman 
Date:   2016-05-03T20:39:58Z

HAWQ-713 Make lc_numeric guc to have GUC_GPDB_ADDOPT




---
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.
---

HAWQ YARN RPC Errors

[Gagan Brahmi]

Hi Team,

Do we have some recommended tuning for the RPC warning/errors
encountered intermittently?

The error which is seen is the following:

WARNING:  Sync RPC framework (inet) finds exception raised.
ERROR:  failed to return resource to resource manager, failed to
receive content (pquery.c:991)

This error however, disappears when we retry the query. There are
cases when the query is to be retried more than once.

The error looks to be invoked when COMM2RM_CLIENT_FAIL_RECV is encountered.

The setup is using YARN resource manager. And the following is the
yarn-client configuration used:




  hadoop.security.authentication
  kerberos



  rpc.client.connect.retry
  10



  rpc.client.connect.tcpnodelay
  true



  rpc.client.connect.timeout
  60



  rpc.client.max.idle
  1



  rpc.client.ping.interval
  1



  rpc.client.read.timeout
  360



  rpc.client.socket.linger.timeout
  -1



  rpc.client.timeout
  360



  rpc.client.write.timeout
  360



  yarn.client.failover.max.attempts
  15


  

I would appreciate some recommendations.


Regards,
Gagan Brahmi

[GitHub] incubator-hawq pull request: HAWQ-711. Bugfix for libyarn/libhdfs3...

[xunzhang]

Github user xunzhang commented on the pull request:

https://github.com/apache/incubator-hawq/pull/647#issuecomment-218735009
  
https://travis-ci.org/xunzhang/incubator-hawq/builds/129677006


---
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.
---