[jira] [Closed] (TRAFODION-1854) Trafodion cannot start on nodes with uppercase hostname.

2016-03-09 Thread Eason Zhang (JIRA) 

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

Eason Zhang closed TRAFODION-1854.
--

> Trafodion cannot start on nodes with uppercase hostname.
> 
>
> Key: TRAFODION-1854
> URL: https://issues.apache.org/jira/browse/TRAFODION-1854
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> set the node's hostname to uppercase, in this case it is set to 'H1 H2 H3'
> Trafodion’s .bashrc is setting correctly:
>  
> # These env vars define all nodes in the cluster
> export NODE_LIST=" H1 H2 H3"
> export MY_NODES=" -w H1 -w H2 -w H3"
>  
> /etc/hosts are also set as ‘H1 H2 H3’.
> sqconfig is also set as uppercase hostname.
> when starting trafodion instance, it will report below error in sqmon.log:
> Processing cluster.conf on local host H1
> [SHELL] Shell/shell Version 1.0.1 EsgynDB_Enterprise Release 2.0.0 (Build 
> release [EsgynDB-2.0.0-0-g2ba9dde_Bld402], date 20151121_0002)
>  
> [SHELL] %
> ! Start the monitor processes across the cluster
> startup
> [SHELL] %startup
> [SHELL] Cannot start monitor from node 'H1' since it is not member of the 
> cluster configuration or 'hostname' string does not match configuration 
> string.
> [SHELL] Configuration node names:
> [SHELL]'h1'
> [SHELL]'h2'
> [SHELL]'h3'
> [SHELL] Failed to start environment!
>  
> [SHELL] %
> exit



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

[jira] [Closed] (TRAFODION-1627) 'sqgen' cannot copy files to all nodes.

2016-03-09 Thread Eason Zhang (JIRA) 

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

Eason Zhang closed TRAFODION-1627.
--

> 'sqgen' cannot copy files to all nodes.
> ---
>
> Key: TRAFODION-1627
> URL: https://issues.apache.org/jira/browse/TRAFODION-1627
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: Eason Zhang
>
> 'shell.env', 'mon.env' doesn't exist on Trafodion, but 'sqgen' tries to use 
> 'pdcp' command to copy them to all nodes:
>$PDCP -w ${ExNodeList[@]} -x `uname -n` sqconfig sqshell gomon.cold 
> gomon.warm shell.env mon.env $PWD
> So this 'pdcp' command will fail to execute, all files will not be copied.



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

[jira] [Resolved] (TRAFODION-1860) sqgen failed to execute on CentOS7 system.

2016-03-09 Thread Eason Zhang (JIRA) 

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

Eason Zhang resolved TRAFODION-1860.

Resolution: Fixed

> sqgen failed to execute on CentOS7 system.
> --
>
> Key: TRAFODION-1860
> URL: https://issues.apache.org/jira/browse/TRAFODION-1860
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: Eason Zhang
>
> missing ctime.pl file on CentOS7.
> [trafodion@vmcentos7 ~]$ sqgen   
> Workstation environment - Not a clustered environment
> Can't locate ctime.pl in @INC (@INC contains: 
> /home/trafodion/trafodion-2.0.1/export/lib /usr/local/lib64/perl5 
> /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl 
> /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at 
> ./gensq.pl line 24.



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

[jira] [Commented] (TRAFODION-1869) 'initialized trafodion' failed on CentOS 7.2

2016-03-09 Thread liu ming (JIRA) 

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

liu ming commented on TRAFODION-1869:
-

improper link order of ms.o and mpitmsg.o to build libsbms
CentOS 7.2 dynamic linker will invoke constructor in the order of the link 
order. 
Will fix it soon.

> 'initialized trafodion' failed on CentOS 7.2
> 
>
> Key: TRAFODION-1869
> URL: https://issues.apache.org/jira/browse/TRAFODION-1869
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: liu ming
>Assignee: liu ming
>
> On CentOS 7.2, install Trafodion then run 'initialize trafodion'
> >>initialize trafodion;
> *** ERROR[2034] $Z000HQ0:48: Operating system error 201 while communicating 
> with server process $Z000I2H:52.
> *** ERROR[2013] Server process tdm_arkcmp could not be created on \\NSK - 
> Operating system error 201.
> *** ERROR[2002] Internal error: cannot create compiler.
> *** ERROR[2005] Internal error: from compilation, no errors in diagnostics 
> yet for statement: control query shape hold;
> *** ERROR[8822] The statement was not prepared.
> --- SQL operation failed with errors.
> related core is from tdm_arkcmp
> Core was generated by `tdm_arkcmp SQMON1.1 0 0 022137 $Z000I2H 
> 192.168.0.10:56579 4 0'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x in ?? ()
> Missing separate debuginfos, use: debuginfo-install trafodion-2.0.1-1.x86_64 
> trafodion-2.0.1-devel.x86_64
> (gdb) bt
> #0  0x in ?? ()
> #1  0x7f44a8552fc6 in SB_Thread::Sthr::time () at 
> /home/centos/traf-plus/core/sqf/export/include/seabed/int/thread.inl:115
> #2  0x7f44adebeef4 in fs_int_fs_file_awaitiox (pp_filenum=0x1603034, 
> ppp_buf=0x7ffe5d71b208, pp_xfercount=0x7ffe5d71b1f4,
> pp_tag=0x7ffe5d71b1f8, pv_timeout=6, pp_segid=0x7ffe5d71b206, 
> pv_int=false, pv_ts=false) at fsi.cpp:1301
> #3  0x7f44adeb8a80 in BAWAITIOX (pp_filenum=0x1603034, 
> ppp_buf=0x7ffe5d71b5f8, pp_xfercount=0x7ffe5d71b60c, pp_tag=0x7ffe5d71b5f0,
> pv_timeout=6, pp_segid=0x0) at fs.cpp:563
> #4  0x7f44b5d629e7 in GuaReceiveControlConnection::wait (this=0x1603020, 
> timeout=6, eventConsumed=, ipcAwaitiox=0x0)
> at ../common/IpcGuardian.cpp:2692
> #5  0x7f44b5d643d8 in GuaReceiveControlConnection::waitForMaster 
> (this=0x1603020) at ../common/IpcGuardian.cpp:3603
> #6  0x00406366 in main ()
> (gdb)



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

[jira] [Resolved] (TRAFODION-1865) uninitialized buffer cause Monitor abort in CentOS 7

2016-03-09 Thread liu ming (JIRA) 

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

liu ming resolved TRAFODION-1865.
-
   Resolution: Duplicate
Fix Version/s: 2.0-incubating

jira TRAFODION-1868 takes care of this issue instead.

> uninitialized buffer cause Monitor abort in CentOS 7
> 
>
> Key: TRAFODION-1865
> URL: https://issues.apache.org/jira/browse/TRAFODION-1865
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: liu ming
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> sqstart failed on CentOS.
> The Monitor process abort in CProcessContainer::CProcessContainer() due to 
> failed to create semaphore.
> //create & initialize existing semaphore
> char sem_name[MAX_PROCESS_PATH];
> snprintf(sem_name,sizeof(sem_name), "/monitor.sem.%s", getenv("USER"));
> Mutex = sem_open(sem_name,O_CREAT,0644,0);
> if(Mutex == SEM_FAILED)
> {
> char buf[MON_STRING_BUF_SIZE];
> snprintf(buf, sizeof(buf), "[%s], Can't create semaphore %s!\n",
>  method_name, sem_name);
> mon_log_write(MON_PROCESSCONT_PROCESSCONT_3, SQ_LOG_ERR, buf);
> sem_unlink(sem_name);
> abort();
> }
> sem_name is not initialized and snprintf will not add \0 after copy required 
> bytes.



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

[jira] [Commented] (TRAFODION-1865) uninitialized buffer cause Monitor abort in CentOS 7

2016-03-09 Thread liu ming (JIRA) 

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

liu ming commented on TRAFODION-1865:
-

The root cause is incompatibility of glibc from CentOS 6 to CentOS 7. 
It has no relationship with uninitialized buffer.
The right solution is to build trafodion binary using gcc 4.8 under centOS 7 to 
run it on CentOS 7.
So close this jira now.

> uninitialized buffer cause Monitor abort in CentOS 7
> 
>
> Key: TRAFODION-1865
> URL: https://issues.apache.org/jira/browse/TRAFODION-1865
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: liu ming
>Assignee: liu ming
>
> sqstart failed on CentOS.
> The Monitor process abort in CProcessContainer::CProcessContainer() due to 
> failed to create semaphore.
> //create & initialize existing semaphore
> char sem_name[MAX_PROCESS_PATH];
> snprintf(sem_name,sizeof(sem_name), "/monitor.sem.%s", getenv("USER"));
> Mutex = sem_open(sem_name,O_CREAT,0644,0);
> if(Mutex == SEM_FAILED)
> {
> char buf[MON_STRING_BUF_SIZE];
> snprintf(buf, sizeof(buf), "[%s], Can't create semaphore %s!\n",
>  method_name, sem_name);
> mon_log_write(MON_PROCESSCONT_PROCESSCONT_3, SQ_LOG_ERR, buf);
> sem_unlink(sem_name);
> abort();
> }
> sem_name is not initialized and snprintf will not add \0 after copy required 
> bytes.



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

[jira] [Commented] (TRAFODION-1868) Compatibility with gcc 4.8

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

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

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

GitHub user traflm opened a pull request:

https://github.com/apache/incubator-trafodion/pull/374

[TRAFODION-1868] Compatibility with gcc 4.8

this is partial changes to Trafodion code base in order to make it 
compatible with gcc 4.8.
Gcc 4.8 generally is more strict than gcc 4.4, so Trafodion code need to 
fix all potential issues.
1. variable declared and initialized, but not used anymore
2. suspicious overload of same variable names
3. ld need the required library name to be explicitly added using '-l' 
option
4. some STL/Boost functions replaced with c++11 features in gcc 4.8, so 
remove unnecessary call into boost
So there are a lot of changes, to make this process easier, we decided to 
do this incrementally. Fix small amount of issues each time, easier to code 
review and test.
It must make sure same code compile and work well under gcc 4.4.

This is the first commit for the whole gcc 4.8 support changes.
We already have a successful gcc 4.8 build prototype, and it works well on 
CentOS 7. But there are still more changes, so this is a rather proven way to 
support gcc 4.8.

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

$ git pull https://github.com/traflm/incubator-trafodion TRAFODION-1854

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

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


commit 1ec16451e37fa21e3978a88def5188a6ff22900c
Author: Liu Ming 
Date:   2016-03-10T02:26:07Z

[TRAFODION-1868] Compatibility with gcc 4.8




> Compatibility with gcc 4.8
> --
>
> Key: TRAFODION-1868
> URL: https://issues.apache.org/jira/browse/TRAFODION-1868
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: Steve Varnau
>Assignee: liu ming
>Priority: Minor
>
> Current code will not compile with gcc 4.8. That is the default version on 
> RH/CentOS 7.  This is needed to move to a development environment on CentOS 7.
> There is a 4.4 version of gcc available on 7. The RPM package is 
> compat-gcc-44, I have not tried building on 7.x with older compiler, but will 
> likely work.
> This is not urgent at this time, but we should move toward enabling a newer 
> dev environment.  But this needs to be coordinated with with versions of OS 
> are supported for runtime use of trafodion.



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

[jira] [Work started] (TRAFODION-1868) Compatibility with gcc 4.8

2016-03-09 Thread liu ming (JIRA) 

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

Work on TRAFODION-1868 started by liu ming.
---
> Compatibility with gcc 4.8
> --
>
> Key: TRAFODION-1868
> URL: https://issues.apache.org/jira/browse/TRAFODION-1868
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: Steve Varnau
>Assignee: liu ming
>Priority: Minor
>
> Current code will not compile with gcc 4.8. That is the default version on 
> RH/CentOS 7.  This is needed to move to a development environment on CentOS 7.
> There is a 4.4 version of gcc available on 7. The RPM package is 
> compat-gcc-44, I have not tried building on 7.x with older compiler, but will 
> likely work.
> This is not urgent at this time, but we should move toward enabling a newer 
> dev environment.  But this needs to be coordinated with with versions of OS 
> are supported for runtime use of trafodion.



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

[jira] [Assigned] (TRAFODION-1868) Compatibility with gcc 4.8

2016-03-09 Thread liu ming (JIRA) 

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

liu ming reassigned TRAFODION-1868:
---

Assignee: liu ming

> Compatibility with gcc 4.8
> --
>
> Key: TRAFODION-1868
> URL: https://issues.apache.org/jira/browse/TRAFODION-1868
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: Steve Varnau
>Assignee: liu ming
>Priority: Minor
>
> Current code will not compile with gcc 4.8. That is the default version on 
> RH/CentOS 7.  This is needed to move to a development environment on CentOS 7.
> There is a 4.4 version of gcc available on 7. The RPM package is 
> compat-gcc-44, I have not tried building on 7.x with older compiler, but will 
> likely work.
> This is not urgent at this time, but we should move toward enabling a newer 
> dev environment.  But this needs to be coordinated with with versions of OS 
> are supported for runtime use of trafodion.



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

[jira] [Closed] (TRAFODION-1821) installer ldap config fails to find lapconfigcheck

2016-03-09 Thread Steve Varnau (JIRA) 

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

Steve Varnau closed TRAFODION-1821.
---
   Resolution: Fixed
Fix Version/s: 2.0-incubating

> installer ldap config fails to find lapconfigcheck
> --
>
> Key: TRAFODION-1821
> URL: https://issues.apache.org/jira/browse/TRAFODION-1821
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: installer
>Affects Versions: 2.0-incubating
>Reporter: Steve Varnau
>Assignee: Amanda Moran
> Fix For: 2.0-incubating
>
>
> This failure is visible in daily test jobs. Example: 
> http://traf-testlogs.esgyn.com/PullReq/313/419/jdbc_test-cdh/Install_Start.log
>  
> ***INFO: Checking LDAP Configuration file for errors.
> /usr/lib/trafodion/installer/traf_sqgen: line 76: ldapconfigcheck: command 
> not found
> ***ERROR: traf_authentication_config not configured correctly.
> ***ERROR: Install will continue WITHOUT simple security turned on.
> ***ERROR: Please review wiki for manual steps to setup simple security.
> ***INFO: starting Trafodion instance



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

[jira] [Commented] (TRAFODION-1821) installer ldap config fails to find lapconfigcheck

2016-03-09 Thread Steve Varnau (JIRA) 

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

Steve Varnau commented on TRAFODION-1821:
-

Amanda fixed this in commit 3c45de7c along with several other issues.

> installer ldap config fails to find lapconfigcheck
> --
>
> Key: TRAFODION-1821
> URL: https://issues.apache.org/jira/browse/TRAFODION-1821
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: installer
>Affects Versions: 2.0-incubating
>Reporter: Steve Varnau
>Assignee: Amanda Moran
> Fix For: 2.0-incubating
>
>
> This failure is visible in daily test jobs. Example: 
> http://traf-testlogs.esgyn.com/PullReq/313/419/jdbc_test-cdh/Install_Start.log
>  
> ***INFO: Checking LDAP Configuration file for errors.
> /usr/lib/trafodion/installer/traf_sqgen: line 76: ldapconfigcheck: command 
> not found
> ***ERROR: traf_authentication_config not configured correctly.
> ***ERROR: Install will continue WITHOUT simple security turned on.
> ***ERROR: Please review wiki for manual steps to setup simple security.
> ***INFO: starting Trafodion instance



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

[jira] [Resolved] (TRAFODION-1862) Transaction ID is returned as -1 when using the in memory table for RMS stats

2016-03-09 Thread Selvaganesan Govindarajan (JIRA) 

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

Selvaganesan Govindarajan resolved TRAFODION-1862.
--
   Resolution: Fixed
Fix Version/s: 2.0-incubating

https://github.com/apache/incubator-trafodion/pull/356

> Transaction ID is returned as -1 when using the in memory table for RMS stats
> -
>
> Key: TRAFODION-1862
> URL: https://issues.apache.org/jira/browse/TRAFODION-1862
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: Venkat Muthuswamy
>Assignee: Selvaganesan Govindarajan
> Fix For: 2.0-incubating
>
>
> When a query is executed under transaction, the transaction ID is part of the 
> run time statistics.
> The command "get statistics for qid " returns a valid transaction id.
> However the command "Select * from table(statistics(null, 'QID='))" 
> returns the transId as -1.



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

[jira] [Resolved] (TRAFODION-1763) LOB: Drop schema cascade fails with LOB tables

2016-03-09 Thread Sandhya Sundaresan (JIRA) 

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

Sandhya Sundaresan resolved TRAFODION-1763.
---
Resolution: Duplicate

>  LOB: Drop schema cascade fails with LOB tables
> ---
>
> Key: TRAFODION-1763
> URL: https://issues.apache.org/jira/browse/TRAFODION-1763
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: sql-exe
>Affects Versions: 1.3-incubating
>Reporter: Weishiun Tsai
>Assignee: Sandhya Sundaresan
>
> Drop schema cascade would often fail when there are LOB tables in the schema. 
> This was seen on the v0115 build:
> >>control query default TRAF_BLOB_AS_VARCHAR 'OFF';
> --- SQL operation complete.
> >>control query default TRAF_CLOB_AS_VARCHAR 'OFF';
> --- SQL operation complete.
> >>
> >>create schema mytest;
> --- SQL operation complete.
> >>set schema mytest;
> --- SQL operation complete.
> >>
> >>create table t1 (c1 blob, c2 clob);
> --- SQL operation complete.
> >>drop table t1;
> --- SQL operation complete.
> >>create table t1 (c1 blob, c2 clob);
> --- SQL operation complete.
> >>
> >>create table t2 (c1 blob, c2 clob);
> --- SQL operation complete.
> >>drop table t2 cascade;
> --- SQL operation complete.
> >>create table t2 (c1 blob, c2 clob);
> --- SQL operation complete.
> >>
> >>get tables;
> Tables in Schema TRAFODION.MYTEST
> =
> LOBDescChunks_02733772491394077848_0001
> LOBDescChunks_02733772491394077848_0002
> LOBDescChunks_02733772491394083286_0001
> LOBDescChunks_02733772491394083286_0002
> LOBDescHandle_02733772491394077848_0001
> LOBDescHandle_02733772491394077848_0002
> LOBDescHandle_02733772491394083286_0001
> LOBDescHandle_02733772491394083286_0002
> LOBMD_02733772491394077848
> LOBMD_02733772491394083286
> T1
> T2
> --- SQL operation complete.
> >>
> >>drop schema mytest cascade;
> *** ERROR[1069] Schema TRAFODION.MYTEST could not be dropped.
> --- SQL operation failed with errors.
> ==
> Here is the entire script to reproduce it:
> control query default TRAF_BLOB_AS_VARCHAR 'OFF';
> control query default TRAF_CLOB_AS_VARCHAR 'OFF';
> create schema mytest;
> set schema mytest;
> create table t1 (c1 blob, c2 clob);
> drop table t1;
> create table t1 (c1 blob, c2 clob);
> create table t2 (c1 blob, c2 clob);
> drop table t2 cascade;
> create table t2 (c1 blob, c2 clob);
> get tables;
> drop schema mytest cascade;



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

[jira] [Resolved] (TRAFODION-1848) LOB infrastructure changes to support GC and get rid of unneeded mxlobsrvr process

2016-03-09 Thread Sandhya Sundaresan (JIRA) 

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

Sandhya Sundaresan resolved TRAFODION-1848.
---
Resolution: Fixed

> LOB infrastructure changes to support GC and get rid of unneeded mxlobsrvr 
> process
> --
>
> Key: TRAFODION-1848
> URL: https://issues.apache.org/jira/browse/TRAFODION-1848
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-exe
>Affects Versions: any
>Reporter: Sandhya Sundaresan
>Assignee: Sandhya Sundaresan
> Fix For: 2.0-incubating
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> Need support to compact lob data files after a certain threshold is reached . 
> Deleting or updating a table with lob columns cn cause the lob datafiles to 
> be left with unused holes. These need to be compacted regularly.
> TO simplify the flow of execution, the mxlobsrvr process functionality is 
> being moved into the master executor. There is no need for a spearate process 
> anymore since there isn't going to be a separate storage engine that may need 
> to make calls to this process. The lob file processing  can all be done in 
> the master process itself. 



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

[jira] [Commented] (TRAFODION-1848) LOB infrastructure changes to support GC and get rid of unneeded mxlobsrvr process

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

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

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

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafodion/pull/363


> LOB infrastructure changes to support GC and get rid of unneeded mxlobsrvr 
> process
> --
>
> Key: TRAFODION-1848
> URL: https://issues.apache.org/jira/browse/TRAFODION-1848
> Project: Apache Trafodion
>  Issue Type: Improvement
>  Components: sql-exe
>Affects Versions: any
>Reporter: Sandhya Sundaresan
>Assignee: Sandhya Sundaresan
> Fix For: 2.0-incubating
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> Need support to compact lob data files after a certain threshold is reached . 
> Deleting or updating a table with lob columns cn cause the lob datafiles to 
> be left with unused holes. These need to be compacted regularly.
> TO simplify the flow of execution, the mxlobsrvr process functionality is 
> being moved into the master executor. There is no need for a spearate process 
> anymore since there isn't going to be a separate storage engine that may need 
> to make calls to this process. The lob file processing  can all be done in 
> the master process itself. 



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

[jira] [Created] (TRAFODION-1884) Need to check that copy completed for hbase-trx*jar file

2016-03-09 Thread Amanda Moran (JIRA) 
Amanda Moran created TRAFODION-1884:
---

 Summary: Need to check that copy completed for hbase-trx*jar file
 Key: TRAFODION-1884
 URL: https://issues.apache.org/jira/browse/TRAFODION-1884
 Project: Apache Trafodion
  Issue Type: Bug
  Components: installer
Reporter: Amanda Moran
Assignee: Amanda Moran


traf_*_mods98 needs to check to make sure all nodes have a copy of 
hbase-trx*.jar file. 

If the copy did not happen correctly, then installation will abort. 

This is very important because HBase will have issues if coprocessor settings 
are set but the file has not been copied. 



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

[jira] [Closed] (TRAFODION-1880) Download libhdfs dependency instead of building from source

2016-03-09 Thread Steve Varnau (JIRA) 

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

Steve Varnau closed TRAFODION-1880.
---
   Resolution: Fixed
Fix Version/s: 2.0-incubating

> Download libhdfs dependency instead of building from source
> ---
>
> Key: TRAFODION-1880
> URL: https://issues.apache.org/jira/browse/TRAFODION-1880
> Project: Apache Trafodion
>  Issue Type: Bug
>Reporter: Steve Varnau
>Assignee: Steve Varnau
> Fix For: 2.0-incubating
>
>
> Trafodion build process picks up libhdfs / libhadoop dependencies either from 
> local_hadoop test set-up or by building them from source code.
> Building them from source more than doubles trafodion build time.
> Previously the the hadoop-common binary distro did not contain native 64-bit 
> shared libraries. Now that it does, we can take advantage of that and not 
> build from source code.



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

[jira] [Resolved] (TRAFODION-1854) Trafodion cannot start on nodes with uppercase hostname.

2016-03-09 Thread liu ming (JIRA) 

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

liu ming resolved TRAFODION-1854.
-
   Resolution: Fixed
Fix Version/s: 2.0-incubating

> Trafodion cannot start on nodes with uppercase hostname.
> 
>
> Key: TRAFODION-1854
> URL: https://issues.apache.org/jira/browse/TRAFODION-1854
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: liu ming
> Fix For: 2.0-incubating
>
>
> set the node's hostname to uppercase, in this case it is set to 'H1 H2 H3'
> Trafodion’s .bashrc is setting correctly:
>  
> # These env vars define all nodes in the cluster
> export NODE_LIST=" H1 H2 H3"
> export MY_NODES=" -w H1 -w H2 -w H3"
>  
> /etc/hosts are also set as ‘H1 H2 H3’.
> sqconfig is also set as uppercase hostname.
> when starting trafodion instance, it will report below error in sqmon.log:
> Processing cluster.conf on local host H1
> [SHELL] Shell/shell Version 1.0.1 EsgynDB_Enterprise Release 2.0.0 (Build 
> release [EsgynDB-2.0.0-0-g2ba9dde_Bld402], date 20151121_0002)
>  
> [SHELL] %
> ! Start the monitor processes across the cluster
> startup
> [SHELL] %startup
> [SHELL] Cannot start monitor from node 'H1' since it is not member of the 
> cluster configuration or 'hostname' string does not match configuration 
> string.
> [SHELL] Configuration node names:
> [SHELL]'h1'
> [SHELL]'h2'
> [SHELL]'h3'
> [SHELL] Failed to start environment!
>  
> [SHELL] %
> exit



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

[jira] [Commented] (TRAFODION-1854) Trafodion cannot start on nodes with uppercase hostname.

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

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

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

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafodion/pull/366


> Trafodion cannot start on nodes with uppercase hostname.
> 
>
> Key: TRAFODION-1854
> URL: https://issues.apache.org/jira/browse/TRAFODION-1854
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: foundation
>Reporter: Eason Zhang
>Assignee: liu ming
>
> set the node's hostname to uppercase, in this case it is set to 'H1 H2 H3'
> Trafodion’s .bashrc is setting correctly:
>  
> # These env vars define all nodes in the cluster
> export NODE_LIST=" H1 H2 H3"
> export MY_NODES=" -w H1 -w H2 -w H3"
>  
> /etc/hosts are also set as ‘H1 H2 H3’.
> sqconfig is also set as uppercase hostname.
> when starting trafodion instance, it will report below error in sqmon.log:
> Processing cluster.conf on local host H1
> [SHELL] Shell/shell Version 1.0.1 EsgynDB_Enterprise Release 2.0.0 (Build 
> release [EsgynDB-2.0.0-0-g2ba9dde_Bld402], date 20151121_0002)
>  
> [SHELL] %
> ! Start the monitor processes across the cluster
> startup
> [SHELL] %startup
> [SHELL] Cannot start monitor from node 'H1' since it is not member of the 
> cluster configuration or 'hostname' string does not match configuration 
> string.
> [SHELL] Configuration node names:
> [SHELL]'h1'
> [SHELL]'h2'
> [SHELL]'h3'
> [SHELL] Failed to start environment!
>  
> [SHELL] %
> exit



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