[jira] [Commented] (TRAFODION-2891) fix the bufoverrun Critical error checked by TScanCode

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323529#comment-16323529
 ] 

ASF GitHub Bot commented on TRAFODION-2891:
---

GitHub user xiaozhongwang opened a pull request:

https://github.com/apache/trafodion/pull/1394

[TRAFODION-2891] fix the bufoverrun Critical error checked by TScanCode

fix the bufoverrun Critical error checked by TScanCode

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

$ git pull https://github.com/xiaozhongwang/trafodion TRAFODION-2891

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

https://github.com/apache/trafodion/pull/1394.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 #1394


commit 0166c96321a104636e7dec67eb98b67e931ea84e
Author: Kenny 
Date:   2018-01-11T08:32:39Z

fix the bufoverrun Critical error checked by TScanCode

commit d6573f9c0a1ca7a7f63f76a629e64750a37f038c
Author: Kenny 
Date:   2018-01-12T01:37:08Z

fix the bufoverrun Critical error checked by TScanCode

commit 1fe8890705310df729c35401d53d55531e8e8398
Author: Kenny 
Date:   2018-01-12T04:02:26Z

fix the bufoverrun Critical error checked by TScanCode




> fix the bufoverrun Critical error checked by TScanCode
> --
>
> Key: TRAFODION-2891
> URL: https://issues.apache.org/jira/browse/TRAFODION-2891
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: xiaozhong.wang
> Attachments: Critical_trafodion_tscancode_codecheck.xml
>
>
> access the buffer over run, if the buffer is at end of memory, will be make a 
> core dump 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TRAFODION-2895) Update Messages Guide for range 1700-1999 and some other cleanups

[David Wayne Birdsall (JIRA)]

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

David Wayne Birdsall resolved TRAFODION-2895.
-
   Resolution: Fixed
Fix Version/s: 2.3

> Update Messages Guide for range 1700-1999 and some other cleanups
> -
>
> Key: TRAFODION-2895
> URL: https://issues.apache.org/jira/browse/TRAFODION-2895
> Project: Apache Trafodion
>  Issue Type: Sub-task
>  Components: documentation
> Environment: All
>Reporter: David Wayne Birdsall
>Assignee: David Wayne Birdsall
> Fix For: 2.3
>
>
> The range 1700-1999 is the last remaining range of DDL messages to be updated.
> There are a few issues to fix in earlier ranges as well (for example a few 
> messages have since been added to the code that were not added to the 
> Messages Guide).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TRAFODION-2895) Update Messages Guide for range 1700-1999 and some other cleanups

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322777#comment-16322777
 ] 

ASF GitHub Bot commented on TRAFODION-2895:
---

Github user asfgit closed the pull request at:

https://github.com/apache/trafodion/pull/1388


> Update Messages Guide for range 1700-1999 and some other cleanups
> -
>
> Key: TRAFODION-2895
> URL: https://issues.apache.org/jira/browse/TRAFODION-2895
> Project: Apache Trafodion
>  Issue Type: Sub-task
>  Components: documentation
> Environment: All
>Reporter: David Wayne Birdsall
>Assignee: David Wayne Birdsall
>
> The range 1700-1999 is the last remaining range of DDL messages to be updated.
> There are a few issues to fix in earlier ranges as well (for example a few 
> messages have since been added to the code that were not added to the 
> Messages Guide).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TRAFODION-2890) When using failed connection handle to alloc statement handle, crash happens

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322745#comment-16322745
 ] 

ASF GitHub Bot commented on TRAFODION-2890:
---

Github user asfgit closed the pull request at:

https://github.com/apache/trafodion/pull/1378


> When using failed connection handle to alloc statement handle, crash happens
> 
>
> Key: TRAFODION-2890
> URL: https://issues.apache.org/jira/browse/TRAFODION-2890
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: client-odbc-linux
>Affects Versions: any
> Environment: centos 6.7
>Reporter: XuWeixin
>Assignee: XuWeixin
> Fix For: 2.2-incubating
>
>
> Using odbc to connect server.
> A segment fault happens while calling SQLAllocHandle to alloc statement 
> handle after connection to server fails.
> The reason is the driver manager has not estimated whether the connection is 
> valid or not.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TRAFODION-2861) Remove incubating reference(s) from code base

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322724#comment-16322724
 ] 

ASF GitHub Bot commented on TRAFODION-2861:
---

GitHub user svarnau opened a pull request:

https://github.com/apache/trafodion/pull/1393

[TRAFODION-2861] Backport to release2.2 branch

This includes doc changes for 2.2 docs to be generated without incubating 
references. (Main website is generated from master branch.)

Also includes packaging changes to remove incubating. 2.2.0 will be first 
TLP release.

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

$ git pull https://github.com/svarnau/trafodion tlp_2.2

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

https://github.com/apache/trafodion/pull/1393.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 #1393


commit f077620ae434bfdc115a599a591bec1f5eb7bff6
Author: Steve Varnau 
Date:   2017-12-22T19:23:57Z

[TRAFODION-2857] Web-site changes to remove incubating status

Project status and URL changes.
Email lists and git repo name changes still to come based on infra changes.

commit 6047c512707f72fd32f4b6e7e91bd3834c272b10
Author: Steve Varnau 
Date:   2017-12-29T19:03:25Z

[TRAFODION-2857] Adding repo and email address name changes.

commit 6429a0c2839dd22eefbd6ed368236492e8f730fc
Author: Steve Varnau 
Date:   2018-01-04T20:07:47Z

[TRAFODION-2861][TRAFODION-2869] Remove incubating from release packaging

Remove disclaimer file and incubating string from packaging file names.




> Remove incubating reference(s) from code base
> -
>
> Key: TRAFODION-2861
> URL: https://issues.apache.org/jira/browse/TRAFODION-2861
> Project: Apache Trafodion
>  Issue Type: Sub-task
>  Components: documentation, website
>Reporter: Pierre Smits
> Fix For: 2.3
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (TRAFODION-2884) Trafodion Foundation Scalability Enhancements

[Gonzalo E Correa (JIRA)]

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

Work on TRAFODION-2884 started by Gonzalo E Correa.
---
> Trafodion Foundation Scalability Enhancements
> -
>
> Key: TRAFODION-2884
> URL: https://issues.apache.org/jira/browse/TRAFODION-2884
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: dtm, foundation, installer
>Affects Versions: 2.3
>Reporter: Gonzalo E Correa
>Assignee: Gonzalo E Correa
> Fix For: 2.3
>
>
> Architectural changes are needed in the Trafodion Foundation components to 
> effectively scale above 256 servers.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (TRAFODION-2883) Preliminary Trafodion Foundation Scalability Enhancements

[Gonzalo E Correa (JIRA)]

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

Work on TRAFODION-2883 started by Gonzalo E Correa.
---
> Preliminary Trafodion Foundation Scalability Enhancements
> -
>
> Key: TRAFODION-2883
> URL: https://issues.apache.org/jira/browse/TRAFODION-2883
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: dtm, foundation, installer
>Affects Versions: 2.3
>Reporter: Gonzalo E Correa
>Assignee: Gonzalo E Correa
> Fix For: 2.3
>
>
> Initial changes required to increase the size of Trafodion instance from 256 
> servers to 1024 servers.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TRAFODION-2896) Internal error in stored procedures when a warning is generated in SQL

[Hans Zeller (JIRA)]

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

Hans Zeller resolved TRAFODION-2896.

Resolution: Fixed

Fix checked into Trafodion master on 1/11/2018 with 
https://github.com/apache/trafodion/pull/1384.

> Internal error in stored procedures when a warning is generated in SQL
> --
>
> Key: TRAFODION-2896
> URL: https://issues.apache.org/jira/browse/TRAFODION-2896
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-exe
>Affects Versions: 2.0-incubating
> Environment: Any, however this problem is not always reproducible
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.3
>
>
> Anu and Selva have seen cases of this and we suspect that the problem has to 
> do with the way the UDR server handles return codes from CLI calls it makes. 
> Stored procedures can contain SQL and produce result sets. As part of this, 
> the UDR server makes CLI calls. Right now, it maps any non-zero return codes 
> to internal errors. That is not quite right, warnings should either be 
> returned to the user or ignored, whichever is more appropriate.
> Selva also found that in some cases we do sequences of CLI calls, and if we 
> encounter a warning in an earlier CLI calls, the later ones may return that 
> warning code if the diagnostics aren't cleared in-between. The UDR server 
> often does not clear the diags area, so it may see this issue.
> The fix for these symptoms is to raise an internal error only for true errors 
> in CLI calls, not for warnings. This applies to code in the UDR server, files 
> in core/sql/udrserv.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (TRAFODION-2896) Internal error in stored procedures when a warning is generated in SQL

[Hans Zeller (JIRA)]

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

Work on TRAFODION-2896 started by Hans Zeller.
--
> Internal error in stored procedures when a warning is generated in SQL
> --
>
> Key: TRAFODION-2896
> URL: https://issues.apache.org/jira/browse/TRAFODION-2896
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-exe
>Affects Versions: 2.0-incubating
> Environment: Any, however this problem is not always reproducible
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.3
>
>
> Anu and Selva have seen cases of this and we suspect that the problem has to 
> do with the way the UDR server handles return codes from CLI calls it makes. 
> Stored procedures can contain SQL and produce result sets. As part of this, 
> the UDR server makes CLI calls. Right now, it maps any non-zero return codes 
> to internal errors. That is not quite right, warnings should either be 
> returned to the user or ignored, whichever is more appropriate.
> Selva also found that in some cases we do sequences of CLI calls, and if we 
> encounter a warning in an earlier CLI calls, the later ones may return that 
> warning code if the diagnostics aren't cleared in-between. The UDR server 
> often does not clear the diags area, so it may see this issue.
> The fix for these symptoms is to raise an internal error only for true errors 
> in CLI calls, not for warnings. This applies to code in the UDR server, files 
> in core/sql/udrserv.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (TRAFODION-2897) Invalid name in MySQL log file when using install_local_hadoop

[Hans Zeller (JIRA)]

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

Work on TRAFODION-2897 started by Hans Zeller.
--
> Invalid name in MySQL log file when using install_local_hadoop
> --
>
> Key: TRAFODION-2897
> URL: https://issues.apache.org/jira/browse/TRAFODION-2897
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-general
>Affects Versions: 2.0-incubating
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.3
>
>
> This problem was reported by Wei Jun Lu (韦俊鲁) on Dec 3 on the Trafodion dev 
> list, here is the email:
> From: 韦俊鲁 [mailto:we...@teamsun.com.cn] 
> Sent: Sunday, December 3, 2017 11:59 PM
> To: dev 
> Subject: trafodion question
> question 1:
>  when execute install_local_hadoop: under the directory 
> local_hadoop/log generate a file named "mysql-general.${HOSTNAME}.log", why 
> the HOSTNAME is not replaced by real value?
> how to fix it?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TRAFODION-2897) Invalid name in MySQL log file when using install_local_hadoop

[Hans Zeller (JIRA)]

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

Hans Zeller resolved TRAFODION-2897.

Resolution: Fixed

Fix checked into Trafodion master on 1/11/2018 with 
https://github.com/apache/trafodion/pull/1384.

> Invalid name in MySQL log file when using install_local_hadoop
> --
>
> Key: TRAFODION-2897
> URL: https://issues.apache.org/jira/browse/TRAFODION-2897
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-general
>Affects Versions: 2.0-incubating
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.3
>
>
> This problem was reported by Wei Jun Lu (韦俊鲁) on Dec 3 on the Trafodion dev 
> list, here is the email:
> From: 韦俊鲁 [mailto:we...@teamsun.com.cn] 
> Sent: Sunday, December 3, 2017 11:59 PM
> To: dev 
> Subject: trafodion question
> question 1:
>  when execute install_local_hadoop: under the directory 
> local_hadoop/log generate a file named "mysql-general.${HOSTNAME}.log", why 
> the HOSTNAME is not replaced by real value?
> how to fix it?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (TRAFODION-2879) Core dump due to reference to deallocated memory for EstLogProp object

[Hans Zeller (JIRA)]

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

Work on TRAFODION-2879 started by Hans Zeller.
--
> Core dump due to reference to deallocated memory for EstLogProp object
> --
>
> Key: TRAFODION-2879
> URL: https://issues.apache.org/jira/browse/TRAFODION-2879
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 2.0-incubating
> Environment: Any
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.3
>
>
> This looks like an old bug that was recently found by Eric Owhadi, with a 
> stack trace that looks like this:
> {noformat}
> #5  0x7f23af4264fa in NAHeap::deallocateHeapMemory (this=0x7f237ddd66c0, 
> addr=0x7f236f70fba8) at ../common/NAMemory.cpp:3230
> #6  0x7f23af42207b in NAMemory::deallocateMemory (this=0x7f237ddd66c0, 
> addr=0x7f236f70fba8) at ../common/NAMemory.cpp:1265
> #7  0x7f23ada97cdd in NABasicObject::operator delete (p=0x7f236f70fba8)
> at ../export/NABasicObject.cpp:139
> #8  0x7f23ac37fa24 in EstLogProp::~EstLogProp (this=0x7f236f70fba8, 
> __in_chrg=) at ../optimizer/EstLogProp.cpp:130
> #9  0x7f23ac38117e in IntrusiveSharedRefCount::destroyObjects 
> (
> this=0x7f236f70fbb8) at ../common/SharedPtr.h:226
> #10 0x7f23ac1ce7de in SharedRefCountBase::decrUseCount (
> this=0x7f236f70fbb8) at ../common/SharedPtr.h:136
> #11 0x7f23ac1cb845 in SharedPtr::~SharedPtr (
> ---Type  to continue, or q  to quit---
> this=0x7f2382e8e2d0, __in_chrg=)
> at ../common/SharedPtr.h:280
> #12 0x7f23ac1c591e in IntrusiveSharedPtr::~IntrusiveSharedPtr 
> (
> this=0x7f2382e8e2d0, __in_chrg=)
> at ../common/SharedPtr.h:376
> #13 0x7f23ab92d85a in CmpContext::~CmpContext (this=0x7f2382e8e090, 
> __in_chrg=) at ../arkcmp/CmpContext.cpp:382
> {noformat}
> I suspect that we are trying to delete the CmpContext::emptyInLogProp_ data 
> member here.
>  
> I think this data member is initialized incorrectly:
>  
> - The CmpContext object lives longer than an individual statement
> - Initially, CmpContext::emptyInLogProp_ is a NULL pointer
> - For every statement (or at least for most statements), we set this data 
> member to an object allocated from the statement heap, see 
> CmpStatement::initQueryAnalysis() in file arkcmp/CmpStatement.cpp.
> - We don’t deallocate this data member explicitly, as far as I can see. It 
> gets automatically deleted when we call the destructor or when we assign a 
> different value to the IntrusiveSharedPtr.
>  
> So, what happens is that when we destroy the statement and its heap, we leave 
> a dangling reference to a deallocated object in the CmpContext. As we can see 
> here, when we later destroy the context, we point to an object in deallocated 
> memory.
> We need to do two things to fix this: First, with these shared pointers, we 
> cannot allocate an object from the statement heap without calling the 
> destructor for the object. Second, we cannot point from the CmpContext to an 
> object that is allocated from the short-lived statement heap - at least not 
> beyond the lifetime of the statement.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TRAFODION-2879) Core dump due to reference to deallocated memory for EstLogProp object

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322643#comment-16322643
 ] 

ASF GitHub Bot commented on TRAFODION-2879:
---

Github user asfgit closed the pull request at:

https://github.com/apache/trafodion/pull/1384


> Core dump due to reference to deallocated memory for EstLogProp object
> --
>
> Key: TRAFODION-2879
> URL: https://issues.apache.org/jira/browse/TRAFODION-2879
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-cmp
>Affects Versions: 2.0-incubating
> Environment: Any
>Reporter: Hans Zeller
>Assignee: Hans Zeller
> Fix For: 2.3
>
>
> This looks like an old bug that was recently found by Eric Owhadi, with a 
> stack trace that looks like this:
> {noformat}
> #5  0x7f23af4264fa in NAHeap::deallocateHeapMemory (this=0x7f237ddd66c0, 
> addr=0x7f236f70fba8) at ../common/NAMemory.cpp:3230
> #6  0x7f23af42207b in NAMemory::deallocateMemory (this=0x7f237ddd66c0, 
> addr=0x7f236f70fba8) at ../common/NAMemory.cpp:1265
> #7  0x7f23ada97cdd in NABasicObject::operator delete (p=0x7f236f70fba8)
> at ../export/NABasicObject.cpp:139
> #8  0x7f23ac37fa24 in EstLogProp::~EstLogProp (this=0x7f236f70fba8, 
> __in_chrg=) at ../optimizer/EstLogProp.cpp:130
> #9  0x7f23ac38117e in IntrusiveSharedRefCount::destroyObjects 
> (
> this=0x7f236f70fbb8) at ../common/SharedPtr.h:226
> #10 0x7f23ac1ce7de in SharedRefCountBase::decrUseCount (
> this=0x7f236f70fbb8) at ../common/SharedPtr.h:136
> #11 0x7f23ac1cb845 in SharedPtr::~SharedPtr (
> ---Type  to continue, or q  to quit---
> this=0x7f2382e8e2d0, __in_chrg=)
> at ../common/SharedPtr.h:280
> #12 0x7f23ac1c591e in IntrusiveSharedPtr::~IntrusiveSharedPtr 
> (
> this=0x7f2382e8e2d0, __in_chrg=)
> at ../common/SharedPtr.h:376
> #13 0x7f23ab92d85a in CmpContext::~CmpContext (this=0x7f2382e8e090, 
> __in_chrg=) at ../arkcmp/CmpContext.cpp:382
> {noformat}
> I suspect that we are trying to delete the CmpContext::emptyInLogProp_ data 
> member here.
>  
> I think this data member is initialized incorrectly:
>  
> - The CmpContext object lives longer than an individual statement
> - Initially, CmpContext::emptyInLogProp_ is a NULL pointer
> - For every statement (or at least for most statements), we set this data 
> member to an object allocated from the statement heap, see 
> CmpStatement::initQueryAnalysis() in file arkcmp/CmpStatement.cpp.
> - We don’t deallocate this data member explicitly, as far as I can see. It 
> gets automatically deleted when we call the destructor or when we assign a 
> different value to the IntrusiveSharedPtr.
>  
> So, what happens is that when we destroy the statement and its heap, we leave 
> a dangling reference to a deallocated object in the CmpContext. As we can see 
> here, when we later destroy the context, we point to an object in deallocated 
> memory.
> We need to do two things to fix this: First, with these shared pointers, we 
> cannot allocate an object from the statement heap without calling the 
> destructor for the object. Second, we cannot point from the CmpContext to an 
> object that is allocated from the short-lived statement heap - at least not 
> beyond the lifetime of the statement.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TRAFODION-2881) Multiple node failures occur during HA testing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322606#comment-16322606
 ] 

ASF GitHub Bot commented on TRAFODION-2881:
---

GitHub user zcorrea opened a pull request:

https://github.com/apache/trafodion/pull/1392

[TRAFODION-2881] HA fixes

Fixed multiple problems in monitor Allgather() socket reconnect logic.
- Separated node down detection logic from communication errors and timeouts
  to better handle multiple failure scenarios
- Better handling network resets
- Additional trace information
- Fixed 'node up' hang in monitor shell due to TmSync race condition

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

$ git pull https://github.com/zcorrea/trafodion TRAFODION-2881

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

https://github.com/apache/trafodion/pull/1392.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 #1392


commit e832d827507521998567d4cc5d92e4239007d19a
Author: Zalo Correa 
Date:   2018-01-11T17:32:11Z

[TRAFODION-2881] HA fixes
Fixed multiple problems in monitor Allgather() socket reconnect logic.
- Separated node down detection logic from communication errors and timeouts
  to better handle multiple failure scenarios
- Better handling network resets
- Additional trace information
- Fixed 'node up' hang in monitor shell due to TmSync race condition




> Multiple node failures occur during HA testing
> --
>
> Key: TRAFODION-2881
> URL: https://issues.apache.org/jira/browse/TRAFODION-2881
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Affects Versions: 2.3
>Reporter: Gonzalo E Correa
>Assignee: Gonzalo E Correa
> Fix For: 2.3
>
>
> Inflicting server failure in certain modes will cause multiple monitor 
> process to also bring their nodes down along with the intended target of the 
> test.
> Server down modes:
> init 6
> reboot -f
> shutdown -r now
> shell node down command
> In addition, after a server down, the shell 'node up' command will also fail 
> intermittently. This requires a longevity HA test to down and up nodes over a 
> long period of time like 24-48 hours.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TRAFODION-2905) query id contains null if exec spj through trafci

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322054#comment-16322054
 ] 

ASF GitHub Bot commented on TRAFODION-2905:
---

GitHub user mashengchen opened a pull request:

https://github.com/apache/trafodion/pull/1391

TRAFODION-2905 query id contain null

if stmtLabel is "null" string, then it will skip driver's conditional 
judgment (if (stmtName ==null) throw exception).

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

$ git pull https://github.com/mashengchen/trafodion queryIdNull

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

https://github.com/apache/trafodion/pull/1391.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 #1391


commit b6c7df53cd8f60eeebd3617bb34f338aa1106a82
Author: aven 
Date:   2018-01-11T11:06:25Z

TRAFODION-2905 query id contain null




> query id contains null if exec spj through trafci
> -
>
> Key: TRAFODION-2905
> URL: https://issues.apache.org/jira/browse/TRAFODION-2905
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: client-ci
>Affects Versions: any
>Reporter: mashengchen
>Assignee: mashengchen
> Fix For: 2.3
>
>
> if exec a spj through trafci, the query id will contain null like the 
> following :
> MXID1100989212382344116088906U308T15000_891_null



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (TRAFODION-2905) query id contains null if exec spj through trafci

[mashengchen (JIRA)]

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

mashengchen updated TRAFODION-2905:
---
Summary: query id contains null if exec spj through trafci  (was: trafci 
exec spj will lost query id )

> query id contains null if exec spj through trafci
> -
>
> Key: TRAFODION-2905
> URL: https://issues.apache.org/jira/browse/TRAFODION-2905
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: client-ci
>Affects Versions: any
>Reporter: mashengchen
>Assignee: mashengchen
> Fix For: 2.3
>
>
> if exec a spj through trafci, the query id will be null like the following :
> MXID1100989212382344116088906U308T15000_891_null



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (TRAFODION-2905) query id contains null if exec spj through trafci

[mashengchen (JIRA)]

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

mashengchen updated TRAFODION-2905:
---
Description: 
if exec a spj through trafci, the query id will contain null like the following 
:
MXID1100989212382344116088906U308T15000_891_null

  was:
if exec a spj through trafci, the query id will be null like the following :
MXID1100989212382344116088906U308T15000_891_null


> query id contains null if exec spj through trafci
> -
>
> Key: TRAFODION-2905
> URL: https://issues.apache.org/jira/browse/TRAFODION-2905
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: client-ci
>Affects Versions: any
>Reporter: mashengchen
>Assignee: mashengchen
> Fix For: 2.3
>
>
> if exec a spj through trafci, the query id will contain null like the 
> following :
> MXID1100989212382344116088906U308T15000_891_null



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TRAFODION-2905) trafci exec spj will lost query id

[mashengchen (JIRA)]

mashengchen created TRAFODION-2905:
--

 Summary: trafci exec spj will lost query id 
 Key: TRAFODION-2905
 URL: https://issues.apache.org/jira/browse/TRAFODION-2905
 Project: Apache Trafodion
  Issue Type: Bug
  Components: client-ci
Affects Versions: any
Reporter: mashengchen
Assignee: mashengchen
 Fix For: 2.3


if exec a spj through trafci, the query id will be null like the following :
MXID1100989212382344116088906U308T15000_891_null



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TRAFODION-2847) Hard to locate issue throw dcs log

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321893#comment-16321893
 ] 

ASF GitHub Bot commented on TRAFODION-2847:
---

Github user gpj1987 closed the pull request at:

https://github.com/apache/trafodion/pull/1348


> Hard to locate issue throw dcs log
> --
>
> Key: TRAFODION-2847
> URL: https://issues.apache.org/jira/browse/TRAFODION-2847
> Project: Apache Trafodion
>  Issue Type: Improvement
>Reporter: Gong Pengju
>Priority: Minor
>
> sometimes when dcs met problem , it's hard to locate issue happened in which 
> line and in which thread



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TRAFODION-2886) fix the null pointer Critical error checked by TScanCode

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321882#comment-16321882
 ] 

ASF GitHub Bot commented on TRAFODION-2886:
---

Github user xiaozhongwang commented on a diff in the pull request:

https://github.com/apache/trafodion/pull/1380#discussion_r160870920
  
--- Diff: core/sql/executor/cluster.cpp ---
@@ -2395,7 +2395,7 @@ NABoolean Cluster::checkAndSplit(ExeErrorCode * rc)
 rc);
   
   if ( !next_ || *rc ) {
-if ( ! rc ) * rc = EXE_NO_MEM_TO_EXEC;
+* rc = EXE_NO_MEM_TO_EXEC;
--- End diff --

the last code is:
if (!next_ || rc)
if ( NULL != rc ) *rc = EXE_NO_MEM_TO_EXEC;

the next line is wrong, because the condition !rc is TRUE when rc = NULL, 
so the *rc is incorrect:
if ( !rc ) *rc = EXE_NO_MEM_TO_EXEC;


> fix the null pointer Critical error checked by TScanCode
> 
>
> Key: TRAFODION-2886
> URL: https://issues.apache.org/jira/browse/TRAFODION-2886
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: xiaozhong.wang
>Priority: Critical
> Attachments: Critical_trafodion_tscancode_codecheck.xml
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TRAFODION-2704) JDBC regression test failed by too many statement on the same session

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRAFODION-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321844#comment-16321844
 ] 

ASF GitHub Bot commented on TRAFODION-2704:
---

Github user xwq closed the pull request at:

https://github.com/apache/trafodion/pull/1225


> JDBC regression test failed by too many statement on the same session
> -
>
> Key: TRAFODION-2704
> URL: https://issues.apache.org/jira/browse/TRAFODION-2704
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: Weiqing Xu
>Assignee: Weiqing Xu
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TRAFODION-2904) optionally add leading space when get a number column to display

[liu ming (JIRA)]

liu ming created TRAFODION-2904:
---

 Summary: optionally add leading space when get a number column to 
display
 Key: TRAFODION-2904
 URL: https://issues.apache.org/jira/browse/TRAFODION-2904
 Project: Apache Trafodion
  Issue Type: Improvement
Reporter: liu ming
Assignee: liu ming


SQL>select '|'||80||80||999||'aaa' from dual;
(EXPR)
---
|  80  80999aaa
--- 1 row(s) selected.

Should be:
|8080999aaa




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)